library references should be URIs, not the library name

[kevmoo]

See
https://pub.dartlang.org/documentation/angular/5.0.0-alpha+9/index.html

Doesn't help

Should be

angular.dart
builder.dart
core.dart
di.dart
experimental.dart
security.dart

These are the actual files I'd import.

...and more painfully
https://pub.dartlang.org/documentation/angular_components/0.9.0-alpha+9/index.html

In this case, there are many libraries named module – no way to tell them apart.

Better to have long URIs than ambiguous names...

[jcollins-g]

Yeah, that's a problem.

We should remove all usages of library names in dartdoc. I think this is likely the main thing blocking dart-lang/sdk#32738; most other pieces of the ecosystem either don't care about the library name at all or don't use it for important things.

[kevmoo]

So I went through googleapis and got rid of pointless library XYZ; names - google/googleapis.dart@a4e0b03 – cool 2.19 feature @srawlins !

Guess what?

Before:

After:

We should really fix this!

[kevmoo]

FYI: all of those v1 things map to compute/v1.dart, ml/v1.dart etc etc

[devoncarew]

Here's an example of one of the source files:

https://github.com/google/googleapis.dart/blob/master/generated/googleapis/lib/abusiveexperiencereport/v1.dart

That's currently inferring v1 as the label for the left nav, but I gather (from the issue title) that we want something more like abusiveexperiencereport/v1.dart.

[srawlins]

Whoa. Mega cringe.

[jcollins-g]

What if the import URIs were available via mouseover and on the library pages themselves, and we started warning for duplicate library names in the same package? No matter what compressed form we choose for the left sidebar there are going to be cases where the user will want to override that -- and there already is a way to do that, the library foo; statement. It's true that it has been deemphasized but I doubt it's going to go away entirely as long as part files exist. We might as well make use of it for its ability to label libraries.

[natebosch]

but I doubt it's going to go away entirely as long as part files exist.

We also prefer that part files refer to the library they are part of by URI and not library name.
https://dart.dev/guides/language/effective-dart/usage#do-use-strings-in-part-of-directives