feat: drop support for classic component layout#721
Conversation
aklkv
force-pushed
the
feat/classic-components-layout
branch
from
2664fd9 to
80d654c
Compare
| '/route.js', | ||
| ]); | ||
|
|
||
| // Classic component |
There was a problem hiding this comment.
Should we keep a parts of this test or drop it all together 🤔
There was a problem hiding this comment.
We should drop everything related
|
This is probably OK as long as we're ready to ship a major. But are there other things that we should be coordinating so that we don't do two majors in quick succession, given ember 6.0 is close? |
|
yeah, I mostly want to see where @machty is at with volar stuff, because if we're going to introduce some churn, I'd prefer we do it once with the volar stuff, and then put the v1.4 in bugfix-only mode its own branch (which I guess could happen now if folks have non-breaking bugfixes to PR) |
|
If this was green we would consider merging it. |
|
So long as this only removes support for FYI Volar will initially support Polaris .gts-only projects and then add support for two-file components, at which point we'll only support co-located components and not reinstate |
|
Merging this so i can work atop it as i reinstate loose mode in Volar. |
4 participants
fixes: #720