Stricter linting #159
Merged
Stricter linting #159
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
tchinmai7
approved these changes
Dec 29, 2023
luthermonson
approved these changes
Jan 3, 2024
okokes-akamai
force-pushed
the
stricter_linting
branch
from
ab8260f
to
0b0d5fe
Compare
|
Had to fix a merge conflict, it's all good now, merging. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
There are three issues with linting atm:
I am to fix all these issues in this PR. Note that I had to disable the ginkgo linter, because it flagged issues that we're working on in #158.