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 adds a little utility fieldtype that helps you structure your blueprints and forms. If you've ever encountered awkward field positioning in the CP, especially in combination with conditional fields, this fieldtype is great! I've been using it in several projects, and it's been very useful. I figured it might be a great addition to the core.
The field is very easy to use. Just add it to your blueprint and give it the desired width. The spacer field itself is hidden with CSS
visibility: hidden
.Possible use case for the fieldtype on the frontend:
How a form submission would look like: