Fix linter errors on unkeyed fields #1922
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
asymmetric
force-pushed
the
lorenzo/lint-untyped-keys
branch
from
edd18d8 to
a977dd9
Compare
asymmetric
changed the title
asymmetric
force-pushed
the
lorenzo/lint-untyped-keys
branch
from
a977dd9 to
7ed139b
Compare
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.
The latest
go vetcomplains thatgithub.jparrowsec.cn/weaveworks/scope/report.Sample composite literal uses unkeyed fields. This fixes it.Steps to reproduce: