-
-
Notifications
You must be signed in to change notification settings - Fork 5
Linter: add rule to remove empty then else #1819
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
Open
Karan-Palan
wants to merge
1
commit into
sourcemeta:main
Choose a base branch
from
Karan-Palan:linter/then_else_empty
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
class ThenElseEmpty final : public SchemaTransformRule { | ||
public: | ||
ThenElseEmpty() | ||
: SchemaTransformRule{ | ||
"then_else_empty", | ||
"`then` or `else` with an empty schema does not restrict " | ||
"validation and is likely ineffective"} {}; | ||
|
||
[[nodiscard]] auto | ||
condition(const JSON &schema, const JSON &, const Vocabularies &vocabularies, | ||
const SchemaFrame &, const SchemaFrame::Location &, | ||
const SchemaWalker &, const SchemaResolver &) const | ||
-> SchemaTransformRule::Result override { | ||
return contains_any( | ||
vocabularies, | ||
{"https://json-schema.org/draft/2020-12/vocab/applicator", | ||
"https://json-schema.org/draft/2019-09/vocab/applicator", | ||
"http://json-schema.org/draft-07/schema#"}) && | ||
schema.is_object() && schema.defines("if") && | ||
((schema.defines("then") && schema.at("then").is_object() && | ||
schema.at("then").empty()) || | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. As in the other PR, remember that schemas can be either objects or boolean. You are missing checking if |
||
(schema.defines("else") && schema.at("else").is_object() && | ||
schema.at("else").empty())); | ||
} | ||
|
||
auto transform(JSON &schema) const -> void override { | ||
if (schema.defines("then") && schema.at("then").is_object() && | ||
schema.at("then").empty()) { | ||
schema.erase("then"); | ||
} | ||
if (schema.defines("else") && schema.at("else").is_object() && | ||
schema.at("else").empty()) { | ||
schema.erase("else"); | ||
} | ||
} | ||
}; |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"likely ineffective" is wrong. It is not likely. It does nothing, in all cases.
For consistency with other rules, can you make the message: "Setting the
then
orelse
keywords to the empty schema does not add any further constraint"There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, just to make the error simpler by just talking about a single keyword, can you split this rule into two? One of
then
and one forelse
similar to how we catchthen
withoutif
andelse
withoutif
?