-
-
Notifications
You must be signed in to change notification settings - Fork 385
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
refactoring: Fixing legacy pathnames #2038
Conversation
Codecov ReportBase: 36.56% // Head: 36.47% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #2038 +/- ##
==========================================
- Coverage 36.56% 36.47% -0.10%
==========================================
Files 229 228 -1
Lines 19383 19306 -77
==========================================
- Hits 7088 7042 -46
+ Misses 11460 11438 -22
+ Partials 835 826 -9
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Because it creates a lot of confusion
9970e24
to
9fd565d
Compare
Please check if the PR fulfills these requirements
See how to contribute
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?
Some changes and cleanup on the
legacy
wrt build paths.There is a lot of redundancy in the
legacy
builder, this PR aims to remove all code duplication.What is the current behavior?
No changes in behavior, this PR should be equivalent code change.
What is the new behavior?
Does this PR introduce a breaking change, and is titled accordingly?
No breaking changes
Other information