Platform 2019.11.11
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_nameis nowmodel_schema_name model(s)is nowrelated_model(s)in themodel_createandmodel_updatemutationsuser(s)is nowrelated_user(s)in theuser_createanduser_updatemutations
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_urlnow includes the versions defined in the schema- You can now prefix
layouts/in thelayout_pathproperty layout_pathin EmailNotification is now validated to make sure the layout exists- An
orclause with only one rule in a GraphQL filter is now applied. Before, it was ignored - New system field
content_updated_atonPage, to help refresh the cache more efficiently - The
admin_model_schemamutation accepts "model_schemas" inphysical_file_path - Removed an unnecessary uniqueness validation for the
nameandtypepair of a property - Fixed a crash when you add an
assetsdirectory insideapp/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
formswithout a matching virtual field - Security improvements