Lint proposal: prefer normalised paths in exports

[ash14]

The following are equivalent:

export 'a.dart';

export './a.dart';

The first form seems to be preferred across Dart sources and tooling (although this doesn't seem to be documented explicitly anywhere?).

Having a lint rule enforce consistency here would be great to have.

[dart-github-bot]

Summary: The issue proposes a new lint rule to enforce consistent use of normalized paths in export statements, preferring the simpler form without leading './'. This would align with common practice in Dart codebases and tooling.

[tenhobi]

Similar to #50198

[ash14]

Sounds like we can just compare the normalised path with the input string then?

final good = 'a.dart';
Uri(path: good).path == good; // true
  
final bad = './a.dart';
Uri(path: bad).path == bad; // false

[lrhn]

The Uri class does normalize paths, so it is a way to check if a path is already normalized. It won't necessarily catch all issues, like .//foo.dart, where the underlying file system will likely consider it equivalent to foo.dart, but the Uri class won't.
There is no good way to check for what the file system does.

[ash14]

There's also path.normalize https://api.flutter.dev/flutter/package-path_path/normalize.html?

If that's not suitable for whatever reason, Uri would still flag .//foo.dart as non-normalised which is the expected outcome of the lint rule. The quick-fix may apply the 'wrong' fix but that's an acceptable trade-off IMO.