Type of PR (feature, enhancement, bug fix, etc.)

Enhancement

Description

This proposes to allow morph to accept a resource in lieu of a CSS selector. Any resource will be converted to a string with dom_id.

Before:

morph dom_id(post), "I am a teapot"

After:

morph post, "I am a teapot"

Before:

morph {dom_id(post1) => render(post1), dom_id(post2) => render(post2)}

After:

morph {post1 => render(post1), post2 => render(post2)}

I've also made the Reflex#dom_id helper more powerful than its Rails counterpart, so that it now accepts ActiveRecord relations and arbitrary objects (that get converted to strings):

dom_id(post1) # "#post_1" (the current behaviour)
dom_id(Post.all) # "#posts"
dom_id("teapots", "search") # "#teapots_search"

That's all pretty cool, but with the above in place, we can dial it up.

morph User.first

This is equivalent to:

morph dom_id(User.first), render(User.first)

And, thanks to a quirk in the way that morphdom works, this is now possible:

morph Post.all

This is equivalent to:

morph dom_id(Post.all), "<div id=\"#{dom_id("posts")}\">#{ApplicationController.render(Post.all)}</div>"

morphdom DGAF so long as the outermost container element has the same id as the target. If you happen to be rendering a collection with a partial that lines up with render defaults, we can now infer everything but the collection itself.

Finally, I added a render_collection method to Reflex that developers can use for more complex morphs:

render_collection(render(posts, partial: "home/posts", locals: {pagy: pagy}), "#my_content_div")

<div id="my_content_div">post1post2</div>

Thanks to @RolandStuder for the initial inspiration.

Why should this be added

Developer happiness and the principle of least surprise.

Checklist

• My code follows the style guidelines of this project
• Checks (StandardRB & Prettier-Standard) are passing
• This is not a documentation update