-
Notifications
You must be signed in to change notification settings - Fork 440
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: forcing all search strategies to use vX API whilst releases not supported in named versions #8283
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
…supported in named versions
f2a886d
to
c31939d
Compare
No changes to documentation |
Component Testing Report Updated Jan 15, 2025 10:25 PM (UTC) ✅ All Tests Passed -- expand for details
|
⚡️ Editor Performance ReportUpdated Wed, 15 Jan 2025 22:27:27 GMT
Detailed information🏠 Reference resultThe performance result of
🧪 Experiment resultThe performance result of this branch
📚 Glossary
|
/** @todo remove defined apiVersion once perspective is supported in | ||
* non-experimental content lake API | ||
*/ | ||
apiVersion: 'vX', |
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.
Only actually added this
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.
Looks good to me, would like @juice49 thoughts on this.
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.
Looks good to me!
Description
This was found when migrating admin studio. Currently this change already exists inside
next
(here)vX
is the only current version of the sanity API that supports perspectives and releases. Therefore any studio wishing to use releases must use either the new groq search strategy (which consequentially will usevX
) or must define explicitly that theS.DocumentList
use.apiVersion('vX')
.In the case of admin studio this was going to leave a significant footprint (since a defined apiVersion is used in a great number of areas).
Since this change is ultimately throwaway (once releases and perspective support is brought to a named version of the Sanity API then
vX
overriding is no longer needed), the smaller the wake the better. This felt like the smallest change - using the corel pre-release of sanity will override the api version for all searches tovX
.Important
Since this is a temporary change whilst releases is only on
vX
, I've already created a revert task to undo this overrideWhat to review
Testing
Verified this against the admin studio:
Admin studio against the current corel tag causes the following error (see here)
Admin studio running locally pointed to this branch resolves the issue (and network interrogation confirms that the api version is successfully being overridden):
Notes for release
N/A