orchestr7/ktoml

Continue parsing on illegal value if default is present?

Open

#209 opened on Apr 14, 2023

View on GitHub
 (1 comment) (0 reactions) (1 assignee)Kotlin (34 forks)auto 404
enhancementgood first issuehelp wanted

Repository metrics

Stars
 (561 stars)
PR merge metrics
 (PR metrics pending)

Description

Is there any way to continue parsing the rest of the file if one of the values is of wrong type but the class contains default value for it? For example when some enum is misspelled

code example:

enum class EnumTest { A, B, C }
@Serializable
data class Foo(
    val a: Int = 5,
    val b: EnumTest = EnumTest.A,
    val c: String = "hello"
)

TOML:

a = 8
b = "D"
c = "world"

Expected result of parsing would be Foo(a = 8, b = EnumTest.A, c = "world")

Current behavior: Value <D> is not a valid enum option. Permitted choices are: A, B, C

My current workaround is to catch the exception, remove the line with specified value and try to parse again. But even that fails if that wrong value is correctly used in another place in the file.

Contributor guide

Research direction
Investigate the parsing logic for missing or invalid enum values and implement fallback to default values when they exist.
Tech stack
kotlin
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Kotlin
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70