react_component_hash always has pre-render true#1077
Merged
Conversation
* Makes no sense to have react_component_hash not use prerrender. * Fixed issue where checking gem existence. * Added docs for react_component_hash
justin808
force-pushed
the
react-component-hash-automatic-prerender
branch
from
75ae868 to
eeddbdb
Compare
Contributor
|
Reviewed 5 of 5 files at r1, 1 of 1 files at r2. Comments from Reviewable |
justin808
added a commit
that referenced
this pull request
May 4, 2018
* react_component_hash always has pre-render true. * Makes no sense to have react_component_hash not use prerrender. * Fixed issue where checking gem existence. * Added docs for react_component_hash
3 tasks
This was referenced Mar 8, 2026
This was referenced Mar 15, 2026
This was referenced Mar 24, 2026
4 tasks
This was referenced Apr 18, 2026
This was referenced May 4, 2026
This file contains hidden or 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
3 participants
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 change is