Skip to content

fix(design): designs saved by a newer build still render - #861

Closed
mortondev wants to merge 1 commit into
feat/portal-design-v2-ai-any-updatefrom
feat/portal-design-v2-stored-reads
Closed

mortondev wants to merge 1 commit into
feat/portal-design-v2-ai-any-updatefrom
feat/portal-design-v2-stored-reads

Conversation

@mortondev

Copy link
Copy Markdown
Member

Stored designs were parsed strictly, so after a rollback a design with a
field or option value only a newer build knows failed to parse: visitors
saw the plain portal and Appearance could not open. Stored reads now set
those aside and log them: an unknown key is dropped, an unknown option
value reads as the default, and a menu item of an unknown kind is left
out. Writes stay strict.


Stack created with GitHub Stacks CLI • Give Feedback 💬

@mortondev
mortondev added this pull request to stack #833 October 31, 2026 13:50
Stored designs were parsed strictly, so after a rollback a design with a
field or option value only a newer build knows failed to parse: visitors
saw the plain portal and Appearance could not open. Stored reads now set
those aside and log them: an unknown key is dropped, an unknown option
value reads as the default, and a menu item of an unknown kind is left
out. Writes stay strict.
@mortondev

Copy link
Copy Markdown
Member Author

Condensed into #880. The stack is now five PRs, #878 to #882; this branch is kept as it was.

@mortondev mortondev closed this Nov 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant