-
Notifications
You must be signed in to change notification settings - Fork 137
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
Projects on embroider don't see the "Non-colocated components" deprecation #2066
Comments
For stable embroider the relevant place is https://github.com/embroider-build/embroider/blob/stable/packages/core/src/module-resolver.ts#L482-L526 Essentially I think we would either need to check your ember-source version and throw the deprecation if your ember-version matches the deprecation, or we could just decide that when you're using embroider this is just deprecated anyway regardless of your ember-source version 🤔 I'm going to add this to the agenda for next week to discuss 👍 |
We discussed this at tooling team weekly meeting and the tentative plan is to emit a deprecation inside the virtual pair component at runtime ( embroider/packages/core/src/virtual-content.ts Lines 67 to 77 in 8e5763c
|
Does this need to be backported? Users can easily upgrade ember-source without upgrading embroider. |
Fixed in #2088. |
A project on latest ember-source (v5.10.2) with many non-colocated component templates wasn't seeing any deprecations for those templates. After investigating, I realized
layoutFor
(the method with the deprecation in ember-source) was never called: The project is using embroider -- embroider is resolving the component's templates at build time.Embroider should add this deprecation.
Relevant RFC advancement PR emberjs/rfcs#1040
The text was updated successfully, but these errors were encountered: