-
Notifications
You must be signed in to change notification settings - Fork 131
Refine detection for NNBD cases and tag generated pages with "Null safety" #2221
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
Conversation
|
This is fine. In g3, we will opt to mark |
|
Do we want to go w/ |
|
Yes, please never use the term 'NNDB' externally. The external name is 'null safety'. We recently added tags on pub.dev, I suggest we align with that, so the tag should say 'Null safety' and the tool-tip should say 'Supports the null safety language feature.'. |
|
Awesome, thanks |
`LanguageFeature` was introduced in #2221 for chips indicating null safety. Since we now use chips for other purposes, such as class modifiers, the name is no longer descriptive. This change renames it to `Tag` to better model the general concept of a highlightable tag on an element. This is somewhat related to`Attribute` , and the two could potentially be merged in a future step. Furthermore, `FeatureSet` is removed and its functionality is inlined into `ModelElement`. Finally `ContainerModifier` is extended to store the class modifier description and URL directly, instead of in separate top level maps .

Fixes #2210.
This puts in the basic scaffolding for tagging pages that are documenting NNBD interfaces and (mostly) boilerplate for connecting to analyzer's package list parsing support.
Tagging @mehmetf and @jdkoren as this touched PackageMeta and markdown templates, respectively.
More extensive tests will wait for a followup -- it's not vital that every case is covered for the preview.