Skip to content

Implement Warning Severity Thresholds Configuration #275

Description

@codeZe-us

Sometimes developers only care about critical errors (like INVALID_DESTINATION) and want to ignore minor info warnings (like MEMO_IGNORED_FOR_MUXED), but currently, all warnings are bundled together.

  • Add a minSeverityLevel option (e.g., 'info', 'warn', 'error') to the extractRouting configuration.
  • Filter the output warnings array based on the provided threshold before returning the result.
  • Ensure backward compatibility by defaulting to 'info' (returning all warnings).

Expectation: Consumers can easily tune the noisiness of the validation engine, preventing their UI from being cluttered by non-critical notifications.

Contributor telegram group: https://t.me/+OBaYnjDFA3w0Njdk

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions