Skip to content

What's New

Platform 2020.03.16

Platform · 2020.03.16 · 16 March 2020

ImprovementNew FeatureBug FixDeprecationOn production sites

On production sites

This release lets you find resources by file path and filter users by related records.

Deploy and sync by file path

Insites now finds admin resources such as forms, GraphQL queries and model schemas by physical_file_path. Before, it used other properties, usually the name. This lets the Insites CLI add two things. insites-cli pull is the reverse of deploy. It creates the app/ and modules/ directories from the current state of the database, with the newest naming and without unneeded default values. insites-cli sync also listens for deleted files and acts on them. These CLI changes are released separately.

Reference GraphQL files by full path

Before, app/graphql/my_directory/my_query.graphql was called with {% graphql res = 'my_query' %}. This was the only resource that worked this way. Because names had to be unique, it often forced structures like graphql/module_a/module_a_create.graphql and graphql/module_b/module_b_create.graphql. Now you call it with {% graphql res = 'my_directory/my_query' %}, so both modules can use graphql/module_a/create.graphql and graphql/module_b/create.graphql.

The old way, by name only, still works but is deprecated. It writes this deprecation log: Finding GraphQL query/mutation by only name is deprecated, use full path instead. Replace my_query with my_directory/my_query.

Filter users by related models and related users

The users GraphQL query can now filter by related_model and by related_users. For example, find all company owners whose company has the property codename set to ES or FI. Or find all users whose boss has the first name John.

Also in this release

  • Fixed the uniqueness validation for a user property
  • Fixed edge cases where content_updated_at was always updated, even when the content did not change directly
  • {% assign = %} now throws a syntax error