Skip to content

Guard spec.convert() against throwing #131

Description

@DmitrySharabin

spec.parse() calls are now guarded with try/catch (#129), but spec.convert() can also throw on values that parsed successfully but aren't valid input for the conversion step.

We should apply the same warn-and-degrade pattern to spec.convert() calls.

Should we degrade/fall back to the parsed value (that is correct on that step)?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions