Platform 2019.12.30
On production sites
This release lets a request choose the page format with a header and makes GraphQL errors easier to read.
Pick a page format with the Content-Type header
You no longer need to put the format in the URL to reach a page that is not html. Before, app/views/pages/hello.json.liquid only worked at https://example.com/hello.json, even when the request sent the Content-Type: application/json header. Now Insites looks for the json page first. If it is not there, it falls back to html, so existing sites keep working.
Also in this release
- Clearer error messages for GraphQL errors caused by invalid database queries
- The
graphqltag can now be closed with{%- endgraphql -%}. Before, this caused a Liquid error - Fixed edge cases when using
sortin GraphQL queries that userelated_modelsorrelated_users