Repository navigation
fix(vue): declare inline typed page props before rendering - #777
Merged
Merged
Conversation
cpojer
marked this pull request as ready for review
November 11, 2026 00:44
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.
Refs #773
A Vue page could lose optional props that were absent from its first response. Declare keys from inline
defineProps<{ ... }>()types before rendering so later responses can use them. Named and inferred types still use the existing runtime path.Verified both request orders in SSR and checked that client navigation shows the new prop while keeping local page state. All 69 Vue tests and both affected type checks passed.