-
Notifications
You must be signed in to change notification settings - Fork 201
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
fix: check licenses fails when project has "direct overridden" dependencies #901
Comments
Hi @mvolpato ! Thanks for opening an issue and letting us know 💙 I did manage to get this to reproduce. However, only when I specified a For example, the following doesn't throw: Valid dependency overridename: foo
environment:
sdk: ">=3.0.0 <4.0.0"
dependencies:
postgrest_errors:
path: ../foo2
dependency_overrides:
postgrest_errors: ^0.1.0 Whereas, the following does: Invalid usage of dependency overridename: foo
environment:
sdk: ">=3.0.0 <4.0.0"
# dependencies:
# postgrest_errors:
# path: ../foo2
dependency_overrides:
postgrest_errors: ^0.1.0 Can you try ensuring those dependencies in your |
Hi @alestiago, all my overrides are path dependencies managed with melos. We do not set specific |
I can confirm this issue when using |
This should be fixed in the next release, to keep an eye on the latest releases refer to the Very Good CLI Releases page. Edit: 0.19.1 is out and should fix this issue. |
Description
When running
very_good packages check licenses
on a project whosepubspec.lock
has "direct overridden" dependencies, the command fails with "Null check operator used on a null value".Tested with
very_good --version
0.18.0.Steps To Reproduce
very_good packages check licenses
;Expected Behavior
A report on licenses for the project.
Actual Behaviour
Additional Context
I removed all the "direct overridden" entries in my
pubspec.lock
and the command run successfully.I think the issue might be fixed when a new version of
pubspec_lock
is released, see alexei-sintotski/pubspec_lock#33. This issue has a PR that solves it.The text was updated successfully, but these errors were encountered: