Support custom render logic in regform fields #6967
Merged
Conversation
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
ThiefMaster
force-pushed
the
reg-render-custom-fields
branch
from
642318f to
6f3e63a
Compare
ThiefMaster
force-pushed
the
reg-render-custom-fields
branch
5 times, most recently
from
a9a8bc5 to
ae817d6
Compare
ThiefMaster
force-pushed
the
reg-render-custom-fields
branch
from
ae817d6 to
21435fd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 is a nicer implementation of #6901 which does not rely on rather convoluted template hooks.
It could also be used later to move the field-specific render logic from the various templates into the field classes, and maybe use one template (module) per field for the more complex fields that need custom markup.