[6.x] Port the entry edit page to Inertia - #19389
Draft
brianjhanson wants to merge 1 commit into
Draft
Conversation
An error occurred while trying to automatically change base from
feature/forms
to
6.x
August 10, 2026 22:08
brianjhanson
changed the title
📚 Storybook previews@craftcms/ui — open Storybook No changed components detected in this Storybook. resources/js — open Storybook No changed components detected in this Storybook. |
brianjhanson
force-pushed
the
feature/inertia-edit-entry
branch
from
August 11, 2026 19:56
420e109 to
129fd0e
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
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.
Description
Ports the full-page entry edit screen to Inertia, rendering the field layout through the Form system.
ElementEditViewModelis the shared payload for element edit screens, mirroringContentIndexViewModel: public methods are payload keys, and element types extend it with their own keys plus asaveUrl().EntryEditViewModelandcontent/Edit.vueare the entry-specific pieces, whileuseElementEditPageandElementEditPage.vuehold the shared client pipeline so the remaining element types only supply what their save action needs.The field layout is compiled to a
FormPayloadthrough the sameFieldLayoutCompilerthe legacy editor and slideouts already use, and rendered byFormRenderer. Saving posts through Inertia to the existingentries/save-entryaction — the Form payload submits ordinary nested input names, so the save controller reads it without a translation layer.Drafts, revisions, and provisional drafts still fall through to
EditElementController, keeping their notices and apply/revert controls intact until those screens are ported later in this stack. That controller also continues to serve slideouts and the element types that haven't been ported.The sidebar meta fields remain a server-rendered island here and move onto the Form system in #19390.