Skip to content

Unpodded components #1173

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

Open
wants to merge 8 commits into
base: master
Choose a base branch
from
Open

Unpodded components #1173

wants to merge 8 commits into from

Conversation

ijlee2
Copy link

@ijlee2 ijlee2 commented May 27, 2025

Background

We use and maintain a fork of ember-table at work, and noticed that the pod structure is still used for components. Generally speaking, [email protected] removed pod support for components, so ember-table may end up becoming a blocker to developers who want to update Ember to v6.

I suspect that the ember-release scenario (i.e. 6.4.0) is currently passing, because the classic components make use of the layout key. Removing the pod structure now would help maintainers and contributors glimmerize these components (Glimmer + pod doesn't work) and introduce the v2 addon format.

What changed?

I introduced the flat component structure, which is the default structure in Ember Octane and works without an issue in v2 addons.

Note

You can ignore the first 7 commits. Once #1172 is merged, I'll rebase this branch so that only the last commit remains.

I didn't remove the pod structure in tests/dummy. ember-cli-addon-docs hadn't been set up for local development, so I wouldn't have been able to test the unpodding easily.

@ijlee2 ijlee2 marked this pull request as ready for review May 27, 2025 06:44
@ijlee2 ijlee2 force-pushed the unpod-components branch from 8a0e277 to 432d814 Compare May 27, 2025 07:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant