Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for overriding validation severity #1890

Merged
merged 1 commit into from
Aug 2, 2023
Merged

Conversation

mtdowling
Copy link
Member

Issue #, if available: Closes #856

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@mtdowling mtdowling force-pushed the severityOverrides branch 2 times, most recently from 595b5ad to 98bdf6f Compare July 28, 2023 21:10
@mtdowling mtdowling marked this pull request as ready for review July 28, 2023 21:33
@mtdowling mtdowling requested a review from a team as a code owner July 28, 2023 21:33
severityOverride cannot set an event to SUPPRESSED. Use suppressions
for that. It cannot lower the severity of an event, only elevate. This
prevents a backdoor for disabling built-in validation or ignoring
ERROR events.

Closes #856
@mtdowling mtdowling merged commit a8c4203 into main Aug 2, 2023
11 checks passed
@mtdowling mtdowling deleted the severityOverrides branch September 11, 2023 18:21
mtdowling added a commit that referenced this pull request Feb 7, 2024
There was a regression in #1890 that allowed ERROR events to be
suppressed. This was not intentional and we do not want to remove this
restriction. ERROR events indicate that the model is in an unusable
state because it violates a MUST in the spec or some other necessary
requirement to make it usable (like referring only to shapes that
exist).

New test cases have been added to guard against this regression in
the future.

Closes #2128
mtdowling added a commit that referenced this pull request Feb 7, 2024
There was a regression in #1890 that allowed ERROR events to be
suppressed. This was not intentional and we do not want to remove this
restriction. ERROR events indicate that the model is in an unusable
state because it violates a MUST in the spec or some other necessary
requirement to make it usable (like referring only to shapes that
exist).

New test cases have been added to guard against this regression in
the future.

Closes #2128
mtdowling added a commit that referenced this pull request Feb 7, 2024
There was a regression in #1890 that allowed ERROR events to be
suppressed. This was not intentional and we do not want to remove this
restriction. ERROR events indicate that the model is in an unusable
state because it violates a MUST in the spec or some other necessary
requirement to make it usable (like referring only to shapes that
exist).

New test cases have been added to guard against this regression in
the future.

Closes #2128
hpmellema pushed a commit to hpmellema/smithy that referenced this pull request Feb 22, 2024
There was a regression in smithy-lang#1890 that allowed ERROR events to be
suppressed. This was not intentional and we do not want to remove this
restriction. ERROR events indicate that the model is in an unusable
state because it violates a MUST in the spec or some other necessary
requirement to make it usable (like referring only to shapes that
exist).

New test cases have been added to guard against this regression in
the future.

Closes smithy-lang#2128
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Promote certain failures to fail the build (was "Fail build when using Unreferenced shapes")
2 participants