ember-elsewhere: Block form of to-elsewhere?
I find myself wanting to use ember-elsewhere in a situation where I have some inline content that I want to “transport” to a sidebar. I could make that content a component but the sidebar and main content are so contextually tied I’m not really super keen on doing that.
Is it possible to have an block component version of to-elsewhere:
{{#to-elsewhere named='sidebar'}}
lorem ipsum sidebar
{{/to-elsewhere}}
lorem ipsum main content window
About this issue
- Original URL
- State: open
- Created 8 years ago
- Reactions: 35
- Comments: 23 (15 by maintainers)
Commits related to this issue
- Merge pull request #2 from kaspiCZ/include-forgotten-fastboot-service Included fastboot service for the check to work — committed to zonkyio/ember-elsewhere by bobisjan 7 years ago
The most relevant work is https://github.com/emberjs/rfcs/blob/master/text/0226-named-blocks.md.
The RFC is merged, and I’m pretty sure the implementation is already working in glimmer-vm. I don’t know what the next step is to turn it on in ember.
I am open to deprecating in favor of ember-stargate. We could give people an easy upgrade by updating this addon to use stargate under the hood. It would make ember-elsewhere into a tiny compatibility layer.
Here’s a very crude POC of that https://github.com/ming-codes/ember-elsewhere-block-form