-
Notifications
You must be signed in to change notification settings - Fork 532
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
feat: update reachability level from "no info" to "no path found" #1609
Conversation
Expected release notes (by @darmalovan) features: fixes: others (will not be included in Semantic-Release notes):
|
Going to be merged tomorrow (10.2) |
@@ -130,6 +130,16 @@ Below are flags that are influencing CLI behavior for specific projects, languag | |||
|
|||
- `--configuration-attributes`=<ATTRIBUTE>[,<ATTRIBUTE>]...: | |||
Select certain values of configuration attributes to resolve the dependencies. E.g. `buildtype:release,usage:java-runtime` | |||
|
|||
- `--reachable`: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this really only for gradle?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And maven (it's already there for maven)
What does this PR do?
Some small improvements around reachability:
--reachable
flag.Where should the reviewer start?
How should this be manually tested?
Any background context you want to provide?
What are the relevant tickets?
https://snyksec.atlassian.net/browse/FLOW-613
https://snyksec.atlassian.net/browse/FLOW-589
Screenshots
Additional questions