Lints to prefer project root path import

[predatorx7]

I was wondering if you'd consider adding a new lint rule to package:lints that would encourage the use of project root path imports over relative or package imports.

Just to illustrate, currently Dart supports these import styles:

1. Relative import

import '../../core/logger.dart';

2. Package import

import 'package:core/logger.dart';

3. Project root import

import '/core/logger.dart';

I personally find the project root imports (/core/logger.dart) to be quite beneficial for code clarity and maintainability, especially in larger projects. They make it immediately clear where a file resides within the project structure, regardless of the current file's location.

Would the team be open to the idea of a lint rule that suggests (and ideally provides a dart fix for) preferring these project root path imports?

If you think this is something worth exploring and you'd like some help with it, I'd be happy to volunteer some time to contribute! 🙌🏼

Thanks for considering this! 🙏

[lrhn]

Not a lint I'd ever recommend to anyone. It's just a style, it's not inherently better or worse.

Or rather, it's worse if it's enforced for all imports, including those in the same directory or a sub-directly.
It would presumably only apply to imports starting with ../. (Otherwise I'd be actively against such a lint.)

Using an absolute /core/logger.dart keeps working if you move the importing file.
Using a relative ../core/foo.dart keeps working if you move both files, by renaming a common parent directory.

[predatorx7]

It would presumably only apply to imports starting with ../. (Otherwise I'd be actively against such a lint.)

Yeah, I agree. I prefer this for imports starting with ../.