-
Notifications
You must be signed in to change notification settings - Fork 3k
Allow library configs to override target configs #6658
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
Conversation
Please review travis failures and jenkins CI |
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. Cc @sg-
These definitely need fixing. |
Agreed. I'm working on it. |
/morph build |
Build : SUCCESSBuild number : 1791 Triggering tests/morph test |
Exporter Build : ABORTEDBuild number : 1439 |
Test : SUCCESSBuild number : 1601 |
/morph export-build |
@theotherjimmy Is this complete? |
Exporter Build : SUCCESSBuild number : 1440 |
@0xc0170 Yes. |
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.
@screamerbg Approval, LGTM as well
Description
The documentation currently claims that libraries are allowed to
override target configuration. This fixes a bug that would prevent a
library configuration from overriding a target configuration.
Application configuration is unaffected.
Pull request type
[X] Fix
[ ] Refactor
[ ] New target
[ ] Feature
[ ] Breaking change