Change Log

Design System Update

Added modal component to the Design System. Click here to view the component on our design system.

New Feature

• export/import internals to be used by the new Instance copy feature coming soon

Bug Fix

• Fix edge case when including invalid partial was causing 500 error
• Regression issues detected on staging

Improvement

• Performance improvements in finding pages
• Better error handling on jwt_encode filter
• Better error handling on wrong MIME types
• Added warning about missing recaptcha key
• Added image and attachment validators to property form
• Gracefully handle restricted property name in admin_* mutations

New Feature

• pos-cli 4.2.5-beta version has been released with direct assets upload on sync
• pos-cli 4.2.4 version has been released with improved logging

Bug Fix

• Fix resolving related models relationships with integer and string property
• Fixed pos-cli deploy command with -d option for direct assets upload

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