Extracting package name from pubspec.yaml

[martingeorgiu]

Is there a reason why the --package is required when the imports are in form of package:?

I was thinking that if in the --path there is pubspec.yaml, we can extract the package name directly from there. Then the parameter could be useful and used only when the --path leads to a folder where there is no pubspec.yaml.

[polina-c]

The original assumption was that most projects use the lint https://dart.dev/tools/linter-rules/prefer_relative_imports
So, this parameter is needed for very rare set of projects.

What you suggested makes sense, but feels as something that is easily breakable by updated format of pubspec.yaml in future versions of dart/flutter.

But may be I am wrong. Feel free to put together PR that implements it. I will review and merge it :)

[martingeorgiu]

We use lint collection lint, which is quite popular, especially for being so strict, and there is used the exact opposite, i.e. always_use_package_imports. To be honest, I don't have any strong preference, but I like how lint package is curated, so I stick to most of its rules and I would say most of the lint users do the same.

So, I would say this is not only for some rare projects. However, I'm also not fond of linking directly to pubspec.yaml notation, but I don't know any other way. If you aren't against it or have a better solution, I would create a PR in the coming weeks once I have time for that.

[polina-c]

Thank you for explaining. Sure, feel free to go ahead with the PR. I will review it.

[polina-c]

Implemented.
Thank you @martingeorgiu

[martingeorgiu]

Did you push/publish it @polina-c? I can't find it anywhere

[polina-c]

Oh, i mixed it with something else. Reopening. Thanks for the catch.🌤