-
-
Notifications
You must be signed in to change notification settings - Fork 91
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
Check host app, then parent, then app for options. #217
base: master
Are you sure you want to change the base?
Conversation
In an in-repo-engine, options are skipped due to the order of how the options are checked. Reverse them so host app options are checked first, then parent options, then app options.
@rwjblue any guidance to get this PR approved/merged? |
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.
Hmm, it seems better in the abstract, to check hostApp
before app
for sure (that is the goal of this PR), but it seems particularly odd to check either of those before parent.options
.
What do you think?
Could you help me understand what From the docs:
I'm unsure, but if the addon is in an in-repo-engine then I assume that:
I'll put together a repo I can share to produce/test this. |
@rwjblue Here's the repo to reproduce the issue: https://github.com/GCheung55/ember-sass-test-repo. Side note, I had to install |
@rwjblue just following up on this in case you've missed it. |
@rwjblue Ping - just following up on this since I'm going through an upgrading round again that will likely be blocked by this issue. |
any updates on this? |
In an in-repo-engine, options are skipped due to the order of how the options are checked.
Reverse them so host app options are checked first, then parent options, then app options.
Should address #182 (comment)