-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Omit code completions for methods that are marked @protected #35449
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
Comments
I feel like this should be a higher priority. Currently it is impossible to expose internal non-private methods to generated code but hide them from the user's auto complete 😔 |
Agree |
I think this also affects |
…en not available. Bug: #35449 Change-Id: Ie8d0b3ba354addbf42d2a4efe9c4dbf318e6c659 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/358120 Reviewed-by: Keerti Parthasarathy <[email protected]> Commit-Queue: Konstantin Shcheglov <[email protected]>
…n not available. Bug: #35449 Change-Id: I9e65a0075a69e0bbc00e814272099a6810b82ed9 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/358261 Commit-Queue: Konstantin Shcheglov <[email protected]> Reviewed-by: Brian Wilkerson <[email protected]>
…mbers when not available. Bug: #35449 Change-Id: I7e02d7fbbc9477ad98dd87327adf3b562fc0fde8 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/358328 Commit-Queue: Konstantin Shcheglov <[email protected]> Reviewed-by: Brian Wilkerson <[email protected]>
It is also applicable for |
The meta package contains an
@protected
annotation for members that should only be invoked from within a class itself. #25841 added analyzer support to warn on all calls to @Protected methods from elsewhere. The present bug request going one step further: omit all @Protected methods from the code completion dialog. This seems like the desired UX given using such a code completion would result in an immediate warning, and this doesn't seem useful.The text was updated successfully, but these errors were encountered: