feat(studio): add Entity form tabs layout metadata - #283
Merged
Merged
Conversation
Allow Entity YAML to author form tabs with column/section markers, persist the layout on entity.form, and render multi-tab forms in Studio while keeping single-tab and flat Entities backward compatible. Co-authored-by: Cursor <cursoragent@cursor.com>
Keep framework-bundled currency metadata aligned with the app-owned tabs dogfood Entity used by Studio form rendering. Co-authored-by: Cursor <cursoragent@cursor.com>
Remove the temporary multi-tab Currency layout used only to exercise Studio form tabs; keep the shared form-tabs feature intact. Co-authored-by: Cursor <cursoragent@cursor.com>
Keep layout markers out of storage fieldType and pad hooks entity rows for the form column so CI matches the new scan shape. Co-authored-by: Cursor <cursoragent@cursor.com>
Point tab fields back at the shared field def; layout markers stay runtime-validated only so fieldType stays aligned with the storage registry. Co-authored-by: Cursor <cursoragent@cursor.com>
thsnkhn
marked this pull request as ready for review
September 22, 2026 08:40
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.
Adds optional Entity tabs with inline fields, column breaks, and section headings. Metadata sync stores the layout in entity.form while only storage fields enter the schema and Record APIs.
Studio shows every explicitly authored tab, including a single tab, and retains the plain form when tabs are absent. Manual Record IDs remain editable. Shared tab primitives provide keyboard navigation and preserve drafts across tabs.
Validation rejects mixed fields/tabs, empty tabs, duplicate identities, and storage settings on layout markers. The editor schema and authoring documentation match the runtime contract. The Entity generator creates one general tab.
Validation: 103 Studio tests, production and embedded builds, Go suite (asset-dependent suites passed after building embedded assets), focused combined metadata/jobs checks, and browser checks for manual IDs, single/flat layouts, keyboard navigation, and draft retention. PostgreSQL integration tests were skipped because DYGO_TEST_DATABASE_URL was not configured.