Release: 28th June 2021
An assortment of good things in this release! A new package to help test the behaviour of your GraphQL API, a document field example, better error messages, accessibility updates and another Prisma update! 🍱
"@keystone-ui/fields": "4.1.2","@keystone-ui/options": "4.0.1","@keystone-ui/pill": "5.0.0","@keystone-ui/popover": "4.0.2","@keystone-ui/toast": "4.0.1","@keystone-next/cloudinary": "6.0.1","@keystone-next/fields": "11.0.1","@keystone-next/keystone": "20.0.1","@keystone-next/testing": "1.0.0","@keystone-next/types": "20.0.1","@keystone-next/utils": "1.0.0",
We’ve shipped a new package called
@keystone-next/testing to help you write tests for your GraphQL API!
Check out the guide on the Keystone website for more details.
We have a new example project for the document field which covers the basic use case of configuring the toolbar, rendering the document field in a front end, and providing custom renderers for the built in data.
Another example showing advanced use cases is in-progress and will be available soon!
GraphQL error messages are far more helpful when running queries. You will now get relevant error messages instead of getting
Cannot assign to read only property 'path' of object '#<Object>'" back.
Thanks @tjbp for contributing this fix!
⚠️ We've tweaked
db.lists APIs on
KeystoneContext to have improved types. If you're using the generated
KeystoneListsTypeInfo type like this:
const lists: KeystoneListsAPI<KeystoneListsTypeInfo> = context.lists;
You will have to change it to use
as like this:
const lists = context.lists as KeystoneListsAPI<KeystoneListsTypeInfo>;
Another set of accessibility improvements in the Admin UI in this release including assorted quality of life and screen reader improvements to Filter pills and dialogs, as well as labels and descriptions.
We've updated our Prisma dependencies to
2.25.0, check out the Prisma releases page for more information.
You can also view the verbose release notes on GitHub.