Related models using array of ids, or filter for users, improvements and fixes
Last edit:
November 11, 2019
NEW
join_on_propertynow accepts array of ids, not only single value (visit tutorial: Loading Related Records From an Array Property)- added
orfilter tousersGraphQL query
IMPROVED
image_presign_urlautomatically includes versions defined in schema- upgraded application server to the newest version
- allowed to prefix
layouts/forlayout_pathproperty - if there is only one rule in
orclause in GraphQL filter then apply it (previously was ignored) - renamed GraphQL argument
model_nametomodel_schema_name - renamed
model(s)torelated_model(s)to avoid confusion inmodel_create,model_updatemutations - renamed
user(s)torelated_user(s)to avoid confusion inuser_create,user_updatemutations - deprecated a bunch of old queries/mutations/fields to not appear in GrahQL editor auto complete list
- in our GraphQL editor, everything is now sorted alphabetically, so it's much easier to find what you are looking for
- added validation to layout_path in EmailNotification to make sure the layout exists
- added new system field
content_updated_attoPageto help invalidate the cache in a more efficient way
FIXED
- accept "model_schemas" in
physical_file_pathfor admin_model_schema mutation - remove unnecessary uniqueness validation for
name,typepair for property - do not allow to override pOS private API endpoints
- do not crash when adding
assetsdirectory withinapp/assets - accessing specific error codes for GraphQL validation errors via
extensions.codes. - properly invalidate layout cache for EmailNotification on sync/deploy/GraphQL mutation
- 500 error when confirmation validation is used in
formswithout defining corresponding virtual field
pos-cli changes
pos-cli changelog is kept separately.