Fix t prefixes not being assigned properly #86
Closed
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
This fixes two changes I made to our t-prefixes that broke things: 1. overriding `ActionView::Base#capture` meant that we'd fire on helper calls too — and extract from their block location. 2. overriding `ActionView::Base#render` instead of `ActionView::PartialRenderer#render` meant that we wouldn't accurately assign the prefix to each render in a collection. Note: we're leveraging Rails 6.1+'s `@current_template.virtual_path` to avoid needing to muck with block source_locations or view_paths, Rails has already figured that out for us.
kaspth
force-pushed
the
fix-t-prefix
branch
3 times, most recently
from
d8aef12
to
b3f6374
Compare
Merged
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.
This fixes a change I made to our t-prefixes that broke things: overriding
ActionView::Base#capturemeant that we'd fire on helper calls too — and extract from their block location.Note: we're leveraging Rails 6.1+'s
@current_template.virtual_pathto avoid needing to muck with block source_locations or view_paths,Rails has already figured that out for us.