Feature: Adding a display option in the backend for specific use cases #53
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
|
@SebastianUhlig I'd love this feature. I tried copying your PR contents in my implementation (using a custom fork of my own, so can't just do a checkout), however it is looking weird (using Nova 4). Did you do any improvements since this PR was made?
|
|
Nvm, I figured it out. Classes beginning with |
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 PR has both a feature and a small fix.
The fix takes care of the slightly failed display of table headers in the DetailField when there are no entered names.
I also removed the static 2rem heights per row that led to unfortunate cases when you wanted to go to "show content".
The feature
->colsPerRow(true or false)adds a function to SimpleRepeatable to change the display to rows in the backend. Very useful if you want to have multiple fields under each other and not squeezed next to each other. This was very useful for us, because you ended up not being able to use the text field at all.