fix: static props inference #62
Closed
Conversation
This file contains 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
|
@bautistaaa is attempting to deploy a commit to the trpc Team on Vercel. A member of the Team first needs to authorize it. |
|
cc @KATT |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
KATT
previously approved these changes
Jun 19, 2022
|
@bautistaaa seems to have some |
|
also, if the example is using a helper, it should probably be included in the paths that are displayed on the page |
Was this what you had in mind? Added a SS to the PR description as well |
KATT
approved these changes
Jun 19, 2022
|
@KATT looks like e2e is stuck 😬 |
auto-merge was automatically disabled
October 3, 2022 19:44
Pull request was closed
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.
Description
Example was not inferring static props and resulting in
neverFound this gem buried in an issue and applied the same solution here
vercel/next.js#15913 (comment)