-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Add @protected metadata (annotation) #6119
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
It would be really cool if the Editor had a user-land "plugin" feature so developer can add behavior triggered by annotations. Removed Type-Defect label. |
Added this to the M3 milestone. |
We currently support "build.dart" as a mechanism for generating errors, warnings, and other files based upon annotations and other content in the Dart source files.... which addresses comment 1. Removed this from the M3 milestone. |
Set owner to @bwilkerson. |
What is the mechanism for reporting warnings/errors via build.dart? |
There isn't one. I'm not sure what Dan meant by his comment, but there isn't currently any way to add warnings and errors. Adding such a mechanism is certainly something on our radar, but unfortunately not something we're likely to get to before the end of Q1. |
Removed Area-Editor label. |
This comment was originally written by [email protected] I would be happy with an editor only annotation provided it wouldn't require manual setup for the consumer of your library and it worked with dartdoc. |
Clearly there is interest here: https://code.google.com/p/dart/issues/detail?id=3193 |
Removed this from the Later milestone. |
Removed Oldschool-Milestone-Later label. |
Removed the owner. |
This comment was originally written by [email protected] This looks like a good workaround, I really miss overridable 'private' methods. |
This is now in the |
This is in the spirit of issue #3.
Think of it as a sister to @override.
The text was updated successfully, but these errors were encountered: