Skip to content

What's New

Platform 2019.11.11

Platform · 2019.11.11 · 11 November 2019

ImprovementNew FeatureBug FixDeprecationOn production sites

On production sites

This release renames several GraphQL arguments and makes the GraphQL editor easier to use.

Clearer GraphQL names

To avoid confusion, these names changed:

  • The argument model_name is now model_schema_name
  • model(s) is now related_model(s) in the model_create and model_update mutations
  • user(s) is now related_user(s) in the user_create and user_update mutations

Find things faster in the GraphQL editor

Everything in the editor is now sorted alphabetically. A number of old queries, mutations and fields are deprecated, so they no longer appear in the autocomplete list.

Load related records from an array

join_on_property now accepts an array of ids, not only a single value. The users GraphQL query also has a new or filter.

Also in this release

  • image_presign_url now includes the versions defined in the schema
  • You can now prefix layouts/ in the layout_path property
  • layout_path in EmailNotification is now validated to make sure the layout exists
  • An or clause with only one rule in a GraphQL filter is now applied. Before, it was ignored
  • New system field content_updated_at on Page, to help refresh the cache more efficiently
  • The admin_model_schema mutation accepts "model_schemas" in physical_file_path
  • Removed an unnecessary uniqueness validation for the name and type pair of a property
  • Fixed a crash when you add an assets directory inside app/assets
  • You can read specific error codes for GraphQL validation errors in extensions.codes
  • The layout cache for EmailNotification is now refreshed correctly on sync, deploy and GraphQL mutation
  • Fixed a 500 error when confirmation validation is used in forms without a matching virtual field
  • Security improvements