Change Log

Improvement

• Performance improvements in resolving properties in models/users GraphQL queries
• Performance improvements for nested users in GraphQL queries
• Performance improvements for filtering by property
• Allow to deploy assets only using -d flag
• Add generic layouts for errors + better handling of couple errors which were resulting in "Unhandled low level exception" error message.

Bug Fix

• Do not try to find custom error page on 504 Timeout
• Invoking update_all GraphQL mutations in background in some scenarios
• Do not force modules/ prefix in admin_* GraphQL mutations for physical_file_path
• Filter on related models with date property

####New Features Component

We now have a reusable component for creating Accordions.
For more details visit the documentation here and the design system here.

Improvement

• Major update of internal components like PostgreSQL version, Redis to the newest available versions
• Ability to set user_id and customizable_id as string instead of integer in data import/export
• Migration engine - handle manifest up to date, execute migrations in the order based on timestamp
• Major performance improvement for GraphQL queries which do exact search on properties
• Improve performance of models/users queries by ignoring custom_images/custom_attachments if not requested

New Feature

• Soft deleted objects will be automatically hard deleted after 30 days
• New, improved search on Documentation site

Bug Fix

• Update Google OAuth API version
• Gracefully handle scenario when invalid property is used in related_filter query
• Fix overwriting form variable in partial which ends with form.liquid in some edge case scenarios
• Fix [parse_json] tag to appear in documentation
• Fix edge case scenario in the import mutation, which could impact performance of the instance in a negative way

Improvement

• added useful debugging information to the [log] tag, like Page slug, partial path, logged in user id etc.
• made sort deterministic by always sorting by id as extra parameter
• performance of some GraphQL queries/mutations

Bug Fix

• names of old resources were causing issues when used as model schema name for form submissions and export
• updating import/export mapping for foreign keys stored directly as user property

Improvement

• show a warning in pos-cli logs when adding/updating a profile via GraphQL/form which does not exist
• error handling of BadRequest, for example, when invalid JSON is provided as parameters to Page
• data export will include user level properties as well

Bug Fix

• assigning properties to user profiles in some scenarios
• sorting by updated_at in some admin_* queries
• [jwt_decode_and_set_session] mutation will correctly set context.current_user

Improvement

• error messages for various GraphQL errors related to invalid DB queries
• the [graphql tag] can now be closed using the {%- endgraphql -%} tag (with dashes). Previously, it was causing a Liquid error.
• pos-cli changelog is [kept separately].

New Feature

• use Content-Type header to determine the [Page format]
• Previously, it was required to explicitly provide the format in the URL to access a page with a different format than html, for example, app/views/pages/hello.json.liquid was accessible via https://example.com/hello.json, even if you made the request using the Content-Type: application/json header. Now, in such a scenario, we will try to load the page with the format json first, and if it's not available, we fall back to html for backwards compatibility.

Bug Fix

• edge case scenarios related to using sort in GraphQL queries when related_models / related_users was used

Improvement

• Last edit:
• Page slug uniqueness validation will generate warning instead of error which prevents deploy
• Performance of related_models filtering
• pos-cli changelog is [kept separately].

New Feature

• value_int, value_float and value_boolean for JSONB property resolver, which is used for example in metadata in admin_* mutations

Improvement

• [context variable] is now available inside [migrations]
• requests made to the pOS private API (for example to /api/graph) won't be redirected if made against different domain than default
• GraphQL mutations *_delete_all mark objects as deleted sync instead of async
• [attachment_presign_url] url to direct S3 upload attachments with possibility for example to specify whether it is private or public
• error message for GraphQL syntax error would clearly state it is GraphQL error
• pos-cli changelog is [kept separately].

New Feature

• add possibility to users and models GraphQL queries to [filter related_models and related_users]
• new Liquid tag [print], which bypasses built-in sanitization

Bug Fix

• importing user_profiles using [data import] and fix edge case issue related to importig array property
• nesting graph queries inside pages directory causing 500 error

Improvement

• Profiler percentage output for [Profiling Slow Pages]
• It is now easier to spot bottlenecks in profiler output.
• pos-cli changelog is [kept separately].

New Feature

• Update Page based on physical_file_path instead of slug.
• This fixes the UX issue when pos-cli sync was enabled, modifying slug/format/method could create duplicated Page objects with the same physical file path.
• It also fixes the UX issue which allowed you to have multiple Pages with the same slug - now uniqueness validation error will be triggered.
• Last but not least - slug became optional - by default path to page will correspond to file path. For example /hello/world will display content of app/views/pages/hello/world.html.liquid, previously you had to define the slug as follows:
• `---
• slug: hello/world

• Hello World
• `

Bug Fix

• Avoid race condition in *_delete_all mutations - since actual deletion takes place in the background, make sure that users created between scheduling a background task and executing it won't be deleted.

Improvement

• model_* mutations return Graph::Types::Model object instead of Customization
• performance of user_* mutations invoked without a form, on Instances with many UserProfiles and ModelSchemas (in some scenarios it is now faster - the improvement depends on the number of UserProfiles/ModelSchemas)
• pos-cli changelog is [kept separately].

New Feature

• special route for service workers
• You can put a file named serviceworker.js (or sw.js) in the app/assets directory and access it via https://www.example.com/serviceworker.js (or https://example.com/sw.js). In case you need more files to be accessible this way, you can add numbers to the filename, for example serviceworker-1.js, serviceworker-2.js, etc.
• Developer guide icon
• For more information, check out our [Service Workers] topic.

Bug Fix

• handle operation name from GraphiQL editor when multiple queries are defined
• edge case random 500 error when acceptance validation was used
• including a partial, which included . in a name, but did not exist (for example {% include "i_do_not.exist" %}), was preventing next partials from being found as well