-
Notifications
You must be signed in to change notification settings - Fork 503
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
property-naming flags extension properties #2024
Milestone
Comments
So when I remove |
Indeed, the annotation causes the check to fail. Same happens with:
|
Problem will either be resolved in |
paul-dingemans
added a commit
that referenced
this issue
May 14, 2023
…er is annotated or prefixed with a modifier Closes #2024
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The following code gets flagged with 0.49.1:
I would not expect this, if you're adding a property via an extension and leveraging
get()
since the value can indeed change inside the implementation.The text was updated successfully, but these errors were encountered: