Draft
Conversation
b07fd22 to
980eca5
Compare
304790f to
4a8e507
Compare
4a8e507 to
ea10499
Compare
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
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.
Changelog
Enhancements
Kirby\Form\Field\SectionField, which serves as a wrapper around our old sections. This makes it possible to use any section in fields by simply writing something like:This enhancement is not just simplifying blueprint setups by being able to only use fields. Section fields can now also make use of when queries and field widths this way for even more options.
<k-model-form>component to handle forms in model views. This new form will now load fields directly into each column without wrapping them in sections. It gets the fields props for the current tab from the refactored model view controller. If there are still old sections, those will now be loaded as fields with the help of the new SectionField (see above) This will drastically reduce the number of async requests to build a model view. It feels a lot snappier in general, but when there are slow, complex fields, the initial loading time for a view might feel a bit longer.Breaking changes
tabresponse in model views no longer contains section definitions. The hierarchy is nowtab > column > fields. All old sections are automatically converted to section fields.