-
Notifications
You must be signed in to change notification settings - Fork 125
Rearrange SDK PackageMeta instantiation to be similar to normal packages #1639
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
…e truly need this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Deferring of course to folks with a bit more context who may have concerns of substance but the logic LGTM!
@@ -104,7 +104,8 @@ void main() { | |||
}); | |||
|
|||
test('sdk name', () { | |||
expect(sdkAsPackageGraph.name, equals('Dart SDK')); | |||
expect(sdkAsPackageGraph.name, equals('Dart')); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FWIW: equals('Dart')
can be simplified to 'Dart'
...
Yet another prep for #1610. This is the first one that has real consequences for how docs will appear. To make dartdoc internally consistent, the SDK is now named "Dart", with a kind: "SDK" rather than "Dart Core" with an empty kind, except for where it was called "Dart SDK" in some places...
Other things Dartdoc documents are of kind "package". With this more consistent handling it opens the doors to making categories work the same for both, which is up next.
With this change, most packages will look the same. Flutter's Dart SDK package on the sidebar will call itself "DART" rather than "DART CORE", and the Dart SDK will show up as "Dart" in some places where it didn't before: