![]() And we believe it sets Sanity apart as a true content platform and developer tool. We don’t know about any other CMS or content editing solutions that offer this kind of flexibility. Keep supporting v2 with bug and stability fixes after v3 is generally available.Assist in migrating popular plugins – we’ve already made the most popular v3-ready.Follow up in channels for feedback and support customers and the community in migrating to and using v3.Provide migration guides and improved documentation.While we hope that the new features and possibilities will sweeten the deal, we will also: So, this is the first time in 5 years that you can’t just run sanity upgrade with our latest updates. And creating new APIs was an opportunity to improve and modernize. Removing the Parts System meant we got to design new APIs. And we were stuck on Webpack 3 (from 2017) because it is too hard to upgrade with confidence. ![]() ![]() The Parts system in V2 is under-documented, and it has been hard to decide what should be a public API or not. But to unlock the many improvements with this upgrade, we decided to remove the Parts System in v3 and build new APIs from scratch based on feedback and learnings (and a lot of contemplation). Because let’s face it: breaking changes for code you rely on sucks. Until now, we’ve been able to avoid breaking changes. You can bootstrap a new v3 Studio from the command line and learn how to migrate existing ones in the new docs beta: This upgrade also makes it easier for us to move faster and more reliably in bringing new features to Sanity Studio.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |