Fix type definitions for page components that take props #4219
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.
Sometimes it's convenient for a Redwood page to take props. I use this to pass in optional props so I can mock specific states in Storybook (see https://github.com//zorro-project/zorro/blob/7fc3c1abec3e5296e8cc2e1a5164a177b9d7a16d/redwood/web/src/pages/SignUp/VideoPage/VideoPage.tsx#L15).
Right now, if a Redwood page takes props it fails the
<Route>
typechecks. This PR loosens up the typecheck so it passes.