Render objects in Ruby templates #169
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In a similar vein to recent changes in Rails, this adds a
rendermethod for Ruby-based templates that either calls the existingpartialmethod, or alternatively calls therender_inmethod of an object that's passed. This lets you do:I also added Zeitwerk loading to facilitate Ruby files within the component folders (
src/_componentsas well as any gems which provide a components folder via a source manifest).Hmm…could this mean…will this…?? Let's just say this enables a much bigger announcement in the near future. 😎
Also includes an improved
captureERB helper as well a fix for #72. In addition, typical "Rails-style" block expressions (aka<%= whatever do %>…<% end %>) now work as expected.