TLDR: are default values on parameters and doc comments both planned to be fully unsupported by the macro introspection APIs?
I've been playing around with the latest macro implementation for the past two weeks or so, to experiment with the new APIs to get a feel for the differences from the analyzer APIs.
I've been building two code-gen related packages, and wanted to build them with macros in mind as well (hoping macros could make the UX of the package even better eventually). One of those packages is a cli command/args generator, that can create an ArgParser instance based on the parameters of a function or constructor, like so:
```dart
/// Shows the commit logs.
@CommandMacro()
Future<void> log({
/// Print out the ref names of any commits that are shown.
Decorate decorate = Decorate.auto,
}) async {
await Process.run('git', ['log', decorate.name]);
}
enum Decorate { short, full, auto, no }
// -- GENERATED CODE BELOW --
final logArgParser = ArgParser()
..addOption(
'decorate',
help: 'Print out the ref names of any commits that are shown.',
allowed: ['short', 'full', 'auto', 'no'],
defaultsTo: 'auto',
mandatory: false,
abbr: 'd',
);
```
However, I don't see Doc Comments on any of the introspection APIs, and for the `Parameter`/`ParameterDeclaration` classes, there's a comment that says the `ParameterCode` getter wont expose the default value, despite them both being static at compile time (I'm sure"static" was never meant to apply to comments, but I think the intent of my question still stands lol).
Thanks in advance for any info!
Patt