More generic handling of "special" objects #1554
Labels
P2
A bug or feature request we're likely to work on
type-code-health
Internal changes to our tools and workflows to make them cleaner, simpler, or more maintainable
There are already objects in Dartdoc that we need to treat specially:
Object
andInterceptor
.Future
seems a likely candidate for this handling. Refactor special object handling so it is done consistently, with a table of what (generally SDK) libraries they come from and validation that Dartdoc always has a ModelElement for them.The text was updated successfully, but these errors were encountered: