Adjusting linter settings to avoid misspel error for generated files #275
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
ulucinar
reviewed
Feb 2, 2023
kdibrov
force-pushed
the
linter-fix
branch
2 times, most recently
from
e7c4c06
to
7893250
Compare
sergenyalcin
approved these changes
Feb 3, 2023
There was a problem hiding this comment.
@kdibrov LGTM. This is a critical fix, your contribution is very appreciated. Thank you very much!
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.
Description of your changes
Adjusting misspel to avoid linter errors for autogenerated files. i.e.:
internal/controller/zz_setup.go:252:70:hdinsightis a misspelling ofhindsight(misspell) sparkcluster "github.com/upbound/provider-azure/internal/controller/hdinsight/sparkcluster"I have:
make reviewable testto ensure this PR is ready for review.How has this code been tested