-
Notifications
You must be signed in to change notification settings - Fork 129
Description
I think the only work to do for #2878 is in how to display a constructor which uses super-parameters. Here is an example of a constructor using field formal parameters:
https://api.dart.dev/stable/2.15.1/dart-io/HttpException/HttpException.html
Even though the implementation is const HttpException(this.message, {this.uri});
, dartdoc "desugars" the first parameter to String message
, displaying the type, and linking the type.
I think super-parameters should be the same: super.foo
should desugar to <type> foo
, linking <type>
. Default values should be handled as they are in other signatures.
I think it would be great to link the name of the parameter/field to the field, both for field formal parameters and super-parameters. This would be a separate enhancement though.