Skip to content
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

Properly assign boolean to is_resolved #3152 #3153

Merged
merged 3 commits into from
Jan 17, 2023

Conversation

JonoYang
Copy link
Contributor

This PR fixes an issue where we assigned None, rather than a True or False value to the is_resolved field for Dependencies parsed from a Maven POM.

    * Add new test

Signed-off-by: Jono Yang <jyang@nexb.com>
Signed-off-by: Jono Yang <jyang@nexb.com>
@JonoYang JonoYang force-pushed the 3152-maven-pom-dep-assign-is_resolved branch from f1806f5 to 4ce06b3 Compare November 21, 2022 19:16
@pombredanne pombredanne added this to the v32.0 milestone Jan 6, 2023
Copy link
Member

@AyanSinhaMahapatra AyanSinhaMahapatra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, Thanks!

Test failures seem to be a fluke?

Signed-off-by: Ayan Sinha Mahapatra <ayansmahapatra@gmail.com>
Copy link
Member

@pombredanne pombredanne left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!
Thanks... merging

@pombredanne pombredanne merged commit cc14890 into develop Jan 17, 2023
@pombredanne pombredanne deleted the 3152-maven-pom-dep-assign-is_resolved branch January 17, 2023 08:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants