Skip to content

Improved JSON parsing error messaging #2

@dougbtv

Description

@dougbtv

Feng mentioned during a recent demo that one thing that might not be intuitive to users is how to fix an error that's caused by a JSON parsing error, with an error message such as:

error parsing configuration: invalid character ':' after top-level value

Two thoughts regarding this:

  1. We could potentially wrap / trap this error and give a more general message, maybe something along the lines of "JSON parsing error in config: field, please check that there's valid JSON within"
  2. We could go upstream and update the CNI libraries to provide some better messaging.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions