-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove wrong resolveInput types until fixed #7801
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
🦋 Changeset detectedLatest commit: 92a8c51 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
94c8669
to
8681430
Compare
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 92a8c51:
|
8681430
to
43a9261
Compare
d0180fe
to
0e14676
Compare
610ae59
to
f2e6287
Compare
Co-authored-by: Mitchell Hamilton <mitchell@hamil.town>
061b612
to
8f8916c
Compare
Co-authored-by: Mitchell Hamilton <mitchell@hamil.town>
Co-authored-by: Mitchell Hamilton <mitchell@hamil.town>
Co-authored-by: Mitchell Hamilton <mitchell@hamil.town>
This pull request removes the contextualised type for
resolvedData
inresolveInput
, and it's return type.In a followup change, will will be adding contextualised types back to this method, but as is, the types are misleading in different situations and may be providing a false sense of security about the safety of your code.