Skip to content
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

[FEATURE set-component-template] #18158

Merged
merged 2 commits into from
Jun 30, 2019
Merged

[FEATURE set-component-template] #18158

merged 2 commits into from
Jun 30, 2019

Conversation

chancancode
Copy link
Member

@chancancode chancancode commented Jun 27, 2019

Implements the Ember side of RFC #481.

@chancancode chancancode marked this pull request as ready for review June 27, 2019 20:28
@rwjblue rwjblue changed the title setComponentTemplate [FEATURE set-component-template] Jun 27, 2019
chancancode and others added 2 commits June 27, 2019 17:08
Co-authored-by: Robert Jackson <me@rwjblue.com>
We explicitly added `| undefined` to the return type in the previous commit

Co-authored-by: Robert Jackson <me@rwjblue.com>
@rwjblue
Copy link
Member

rwjblue commented Jun 27, 2019

Fixed merge conflicts

Copy link
Contributor

@pzuraq pzuraq left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generally looks good! Just one minor question, everything else is 👍


function lookupComponent(owner: Owner, name: string, options: LookupOptions): Option<LookupResult> {
if (options.source || options.namespace) {
if (EMBER_MODULE_UNIFICATION) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need these? I thought we'd removed them

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pzuraq - We disabled the flag (though when we did that @chancancode and I had already done the work here to support it) because it was impossible to test either colocation or MU (we only test with all optionals or none) and some aspects of the feature conflicts with MU.

tldr; we haven't removed the MU feature flagged code yet, and just in case we need to salvage parts of it (who knows why) we wanted to leave things roughly in the same basic state before/after this PR

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.

3 participants