-
Notifications
You must be signed in to change notification settings - Fork 44
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
build: Ban extra elses #366
Merged
Merged
Conversation
This file contains 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
AndrewSisley
added
ci/build
This is issue is about the build or CI system, and the administration of it.
code quality
Related to improving code quality
labels
Apr 19, 2022
AndrewSisley
requested review from
orpheuslummis,
jsimnz,
fredcarle and
shahzadlone
April 19, 2022 18:40
Benchmark ResultsSummary
✅ See Better Results...
❌ See Worse Results...
✨ See Unchanged Results...
🐋 See Full Results...
|
Codecov Report
@@ Coverage Diff @@
## develop #366 +/- ##
===========================================
- Coverage 64.99% 64.98% -0.01%
===========================================
Files 80 80
Lines 9185 9183 -2
===========================================
- Hits 5970 5968 -2
+ Misses 2603 2602 -1
- Partials 612 613 +1
|
conventional commit title will be like |
shahzadlone
reviewed
Apr 20, 2022
shahzadlone
reviewed
Apr 20, 2022
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.
LGTM!
shahzadlone
approved these changes
Apr 20, 2022
Do not want to enable these now
If also inverted as it clarifies that the error is secondary to the continue
AndrewSisley
force-pushed
the
sisley/build/I364-else-ban
branch
from
April 20, 2022 03:03
899f4cf
to
ae2fcb0
Compare
Benchmark ResultsSummary
✅ See Better Results...
❌ See Worse Results...
✨ See Unchanged Results...
🐋 See Full Results...
|
shahzadlone
pushed a commit
to shahzadlone/defradb
that referenced
this pull request
Feb 23, 2024
* Add superfluous-else rule to revive linter * Remove default revive linter rules Do not want to enable these now * Remove extra else from CreateDescriptions If also inverted as it clarifies that the error is secondary to the continue * Remove extra else from generate code * Enable revive linter
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
ci/build
This is issue is about the build or CI system, and the administration of it.
code quality
Related to improving code quality
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.
Closes #364
Adds a linter rule prohibiting else clauses from following if statements that always escape, for example:
must become:
Also reworks the 3 current violations of this rule in our codebase