Release: 13th July 2021
More examples, types, and UI rendering tweaks as we push forward towards a general availability release! 🚀
"@keystone-ui/core": "3.1.1","@keystone-next/admin-ui-utils": "5.0.4","@keystone-next/auth": "29.0.0","@keystone-next/cloudinary": "6.0.4","@keystone-next/document-renderer": "4.0.0","@keystone-next/fields": "12.0.0","@keystone-next/fields-document": "7.0.2","@keystone-next/keystone": "22.0.0","@keystone-next/session-store-redis": "3.0.2","@keystone-next/testing": "1.0.2","@keystone-next/types": "22.0.0","@keystone-next/utils": "1.0.2",
We have a new example for custom field views, demonstrating how to create a custom field view for a JSON field. This example allows users to add, edit and remove navigation items from a list:
Be sure to check out all the examples, with more to come.
If an item referenced in a document field is deleted from Keystone, the document field now handles this gracefully. Before an error would be returned when querying the field, which prevents the user from being able to manage the issue.
This release fixes this to simply return
null for the missing item. This also covers the behavior for when a user doesn't have read access for an item.
A variety of UI fixes are in this release when rendering fields in the Admin UI:
- The value of
datapassed to the inline relationship renderer now matches the data returned by the GraphQL query.
- Falsey values of
data.labelare no longer set to
data.idand falsey values of
data.dataare no longer set to
- Fixed the relationship name not being passed to the inline relationship renderer.
- Fixed confusing error when providing fields that don't exist to
displayMode: 'cards'not using labels for related items in the cell view.
We've added generated types for
You can now import these from
.keystone/types (instead of
@keystone-next/types) to get types that are pre-bound to your project's schema.
Another update for Prisma, version
2.26.0, check out the Prisma releases page for more details.
packages-next folder has moved over to
packages as part of our push to a general availability release in the near future!
You can also view the verbose release notes on GitHub.