While waiting for my builds this morning (
) I implemented @emberjs RFC #280 so you can test your apps without the application <div /> on canary now
https://ember-twiddle.com/?numColumns=2&openFiles=twiddle.json%2Cstyles.app.css …



-
-
Another dimension of it is the process is trying to make sure people sinking a lot of effort/work into something that the core team/community aren't actually interested in.
-
Sometimes you will see the "PRs welcomed" sign and spend a lot of effort implementing a feature, just to find out it's philosophically misaligned with the project's goals. It wastes a lot of the contributor's time and also maintainer's resource to review/comment on them.
-
If/when that is not a concern, I think it adds a lot of value to have working prototypes (either in an addon if possible or behind a flag) that people can play with to understand the proposal and its impact.
-
Especially true when evaluating things like ergonomics and ecosystem impact. In this case these proposals are things that we have wanted to do for a long time and has already been circulated with a few core team members, and not really taking away resource from the team.
-
And
@wycats mentioned the implementations are small/contained (not an accident – we built the Glimmer engine with these features in mind so they already existed in the engine for a long time, just need a bit of glue to expose them). -
Same thing with the components manager RFC – we progressed the proposal to a point where we really need some real world implementation feedback to help us break through some conceptual/design bottleneck, so it's been developed behind a flag on master for a while now.
-
Suppose I submit an RFC to add something to Ember, could I implement it behind a flag while the RFC is not accepted yet?
-
Yes, that has definitely been done before. The code still needs to be something maintainers want to merge of course
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.