Skip to content

fix: support legacy and new dependency fields in ScanCode JSON#642

Open
kushal-p16 wants to merge 2 commits intoaboutcode-org:developfrom
kushal-p16:patch-1
Open

fix: support legacy and new dependency fields in ScanCode JSON#642
kushal-p16 wants to merge 2 commits intoaboutcode-org:developfrom
kushal-p16:patch-1

Conversation

@kushal-p16
Copy link

This PR adds backward compatibility for ScanCode dependency fields.

Changes:

  • Added support for legacy field is_resolved
  • Retained support for new field is_pinned
  • Ensures compatibility with both old and new ScanCode JSON outputs

This change is non-breaking and improves robustness when handling different ScanCode versions.

Add support for legacy ScanCode dependency field `is_resolved` alongside the newer `is_pinned` field.

This ensures compatibility with both older and newer ScanCode JSON outputs without breaking existing functionality.

Signed-off-by: KUSHAL P <kushalmys55@gmail.com>
fix: add backward compatibility for dependency field is_resolved

- Support both `is_resolved` (legacy) and `is_pinned` (new)
- Mark `is_resolved` as deprecated
- Improve type documentation for clarity

Signed-off-by: Kushal Prasad <your-email@example.com>
Signed-off-by: KUSHAL P <kushalmys55@gmail.com>
@kushal-p16
Copy link
Author

Hi, I’ve been working on multiple contributions recently and planning to apply for GSoC under the 5C project.

Would love to get feedback or suggestions on areas I should focus on.

Thanks!

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.

1 participant