-
Notifications
You must be signed in to change notification settings - Fork 438
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: fixes schema extraction with nested union refs #8096
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
No changes to documentation |
Component Testing Report Updated Jan 7, 2025 1:01 PM (UTC) ✅ All Tests Passed -- expand for details
|
⚡️ Editor Performance ReportUpdated Tue, 07 Jan 2025 13:04:31 GMT
Detailed information🏠 Reference resultThe performance result of
🧪 Experiment resultThe performance result of this branch
📚 Glossary
|
1b22b56
to
8f6799f
Compare
8f6799f
to
3005a89
Compare
3005a89
to
6ecf11f
Compare
I tried updating the snapshots using
I checked and that's the same on |
6ecf11f
to
d2bba4d
Compare
This was seen in a schema produced by automated tooling. The recursion guard was too strict in this case as the two occurrences of a reference ending up having the same guard path name and extraction would therefore abort before looking inside the second one, instead returning `{}` which would fail when attempting to inspect the name field a little lower down.
d2bba4d
to
aa5f0ad
Compare
This was seen in a schema produced by automated tooling. The recursion
guard was too strict in this case as the two occurrences of a
reference ending up having the same guard path name and extraction
would therefore abort before looking inside the second one, instead
returning
{}
which would fail when attempting to inspect the namefield a little lower down.