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

Don't suggest getters on optional fields or when checking for nil in general #14

Open
iwittkau opened this issue Jan 15, 2025 · 0 comments

Comments

@iwittkau
Copy link

Optional fields are pointers in generated Go code, but the getter returns the value.

So, if you need to check if an optional value was set in a request message, you need to access it directly and check if the field is nil.

Checking a field against nil may be a general use case that shouldn't be discouraged by the linter.

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

No branches or pull requests

1 participant