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

Remove support for non-glimmer template-only components #20685

Merged
merged 1 commit into from
Apr 22, 2024

Conversation

ef4
Copy link
Contributor

@ef4 ef4 commented Apr 22, 2024

The template-only-glimmer-components optional feature became mandatory at 4.0. This removes the implementation for the unreachable branch.

The template-only-glimmer-components optional feature became mandatory at 4.0. This removes the implementation for the unreachable branch.
@ef4 ef4 added the Cleanup label Apr 22, 2024
@ef4 ef4 mentioned this pull request Apr 22, 2024
@ef4 ef4 merged commit aa91346 into main Apr 22, 2024
22 checks passed
@ef4 ef4 deleted the cleanup-template-only-feature branch April 22, 2024 15:56
@boris-petrov
Copy link
Contributor

I don't understand. I updated Ember to 5.10, removed template-only-glimmer-components from config/optional-features.json, and I got:

The template-only-glimmer-components optional feature should be enabled under Octane, run `ember feature:enable template-only-glimmer-components` to enable it

Same for the application-template-wrapper setting. Am I supposed to leave these in the optional-features.json file even though they are not used?

@ef4
Copy link
Contributor Author

ef4 commented Jul 9, 2024

Yeah it looks like that assertion needs to get cleaned up. You can leave the setting in place for now to silence it. If you want to make a PR taking it out it's here:

`* The template-only-glimmer-components optional feature should be enabled under Octane, run \`ember feature:enable template-only-glimmer-components\` to enable it`

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants