Skip to content
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

Handle linted enum values from imported protos #41

Merged
merged 3 commits into from
Mar 11, 2021
Merged

Handle linted enum values from imported protos #41

merged 3 commits into from
Mar 11, 2021

Conversation

ydnar
Copy link
Contributor

@ydnar ydnar commented Mar 11, 2021

Fixes #40.

ydnar added 2 commits March 11, 2021 15:36
This is a test case to verify the bug in #40.
This fixes using imported enum values renamed with (go.lint).all. Fixes #40.
@ydnar ydnar self-assigned this Mar 11, 2021
@ydnar ydnar merged commit 5bb12fb into main Mar 11, 2021
@ydnar ydnar deleted the ydnar/40 branch March 11, 2021 23:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

option (go.lint).all = true; does not work for enum values imported from other package
1 participant