feature - create `params` property and deprecate sending components in a hash
Closed this issue · 0 comments
jenweber commented
Right now, you can send
a hash that includes a component and other data/content. However, this causes issues with tools like embroider, which need to have some assurance that the component exists when it's used on the other end, in from-elsewhere
.
Here's an example:
What we could do is create a new property, params
(or similar) that accepts the hash of models, actions, etc, and send
is the only place where you could put a component:
Then, send
ing a hash could be deprecated, with a very clear migration strategy for the future.