TangibleFieldsRenderer: Centralize fields args formatting#51
Merged
nicolas-jaussaud merged 3 commits intoJul 6, 2026
Merged
Conversation
zinigor
approved these changes
Jul 6, 2026
zinigor
left a comment
zinigor
left a comment
Contributor
There was a problem hiding this comment.
Looks nice, with tests too!
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
2 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.
Currently just a draft as it will conflict if PR#50 is mergedI noticed we currently apply a similar formatting in different places for fields args:
This is just a proposition to centralize this behavior, and make sure we format fields and subfields consistently regardless of where they are rendered
I also added a throw when we attempt to use an unsupported field type as a repeater subfield (here) instead of a silent fallback to text, but it can be changed back if needed