You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to minimally support macros, we need a few bits of work. First, we need dartdoc to not crash when it attempts to document a package with macro applications; that should land with #3687.
After that, I'd like these features:
On the page for a class which has a macro-generated constructor, the constructor is displayed in the main panel and the sidebar, under 'Constructors.'
Bonus - it has a little chip saying something like 'macro-generated.' Design TBD.
Mutatis mutandis for a macro-generated instance method.
A page for a macro-generated constructor is produced.
Mutatis mutandis for a macro-generated instance method.
A macro-generated constructor can be referenced in a doc comment; it results in a valid link in the HTML.
Mutatis mutandis for a macro-generated instance method.
The text was updated successfully, but these errors were encountered:
srawlins
added
type-enhancement
A request for a change that isn't a bug
P1
A high priority bug; for example, a single project is unusable or has many test failures
labels
Feb 28, 2024
After checking 4 of the above 7 boxes, I'm reducing the priority of the remaining work.
srawlins
added
P2
A bug or feature request we're likely to work on
and removed
P1
A high priority bug; for example, a single project is unusable or has many test failures
labels
Mar 11, 2024
In order to minimally support macros, we need a few bits of work. First, we need dartdoc to not crash when it attempts to document a package with macro applications; that should land with #3687.
After that, I'd like these features:
The text was updated successfully, but these errors were encountered: