Skip to content

@internal should disable public_member_api_docs when applied on variables #60617

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

Open
rrousselGit opened this issue Apr 24, 2025 · 1 comment
Labels
area-devexp For issues related to the analysis server, IDE support, linter, `dart fix`, and diagnostic messages. devexp-linter Issues with the analyzer's support for the linter package linter-false-positive P3 A lower priority bug or feature request type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)

Comments

@rrousselGit
Copy link

Consider:

@internal
int a = 42;

This will trigger the public_member_api_docs lint.

This is inconsistent with @internal applied on classes:

@internal
class A{} // No public_member_api_docs lint
```Ï
@rrousselGit
Copy link
Author

The same applies should apply to typedef, constructors, and any other annotated element.

I assume the fix should be as simple as changing visitClassDeclaration to visitAnnotatedNode or something similar :)

@lrhn lrhn added the area-devexp For issues related to the analysis server, IDE support, linter, `dart fix`, and diagnostic messages. label Apr 28, 2025
@srawlins srawlins added P3 A lower priority bug or feature request devexp-linter Issues with the analyzer's support for the linter package type-bug Incorrect behavior (everything from a crash to more subtle misbehavior) linter-false-positive labels Apr 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-devexp For issues related to the analysis server, IDE support, linter, `dart fix`, and diagnostic messages. devexp-linter Issues with the analyzer's support for the linter package linter-false-positive P3 A lower priority bug or feature request type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Projects
None yet
Development

No branches or pull requests

3 participants