-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
fix(fields): fix calendarDay non-nullable input type name #7866
Conversation
🦋 Changeset detectedLatest commit: af76c3a 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 |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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 af76c3a:
|
tested this with the repro example I added in #7865 - can confirm this does fix the issue |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Thanks @acburdine 💙 - this is great |
* fix(fields): fix calendarDay non-nullable input type name * Update .changeset/tasty-lies-move.md Co-authored-by: Mitchell Hamilton <mitchell@hamil.town>
* fix(fields): fix calendarDay non-nullable input type name * Update .changeset/tasty-lies-move.md Co-authored-by: Mitchell Hamilton <mitchell@hamil.town>
* fix(fields): fix calendarDay non-nullable input type name * Update .changeset/tasty-lies-move.md Co-authored-by: Mitchell Hamilton <mitchell@hamil.town>
* fix(fields): fix calendarDay non-nullable input type name * Update .changeset/tasty-lies-move.md Co-authored-by: Mitchell Hamilton <mitchell@hamil.town>
I'm relatively certain this will fix the issue I reported in #7865, but there could be other reasons it was occurring. This just appeared to be the most obvious one.