-
-
Notifications
You must be signed in to change notification settings - Fork 398
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
Some refactorings on library resolution code #1766
Conversation
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.
There are several breaking changes to the exported Go package API. Are those still supposed to be documented for the legacy
packages?
The |
979a13e
to
872d8c2
Compare
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #1766 +/- ##
==========================================
- Coverage 62.86% 62.80% -0.06%
==========================================
Files 218 217 -1
Lines 19462 19454 -8
==========================================
- Hits 12235 12219 -16
- Misses 6145 6150 +5
- Partials 1082 1085 +3
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
There was no need to have it encapsulated in a Command
Removed dependency from types.Context
Instead of skipping include detection later, avoid to add the sources in the queue right from the beginning.
Also remove the reference to the original Library object because it's no more needed.
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.
lgtm
Please check if the PR fulfills these requirements
before creating one)
our contributing guidelines
UPGRADING.md
has been updated with a migration guide (for breaking changes)What kind of change does this PR introduce?
Just some equivalent code change to simplify and make the code more readable.
What is the current/new behavior?
no changes in behavior
Does this PR introduce a breaking change, and is titled accordingly?
No