Change Log

Improvement

• Deploy/sync based on physical_file_path for all admin resources
• Behind the scenes pos-cli was relying on platformOS to find admin resources like forms, graphql queries, model schemas based on different properties, usually name. We improved this functionality and from now on physical_file_path will be used. This allowed us to add two enhancements to pos-cli - pos-cli pull, which would be the reverse of deploy - it will create the app/ and modules/ directory based on current DB state (using the newest naming, without unnecessary default values) and pos-cli sync will also listen to file deletion and act accordingly. Those changes will be released separately, you can follow them at the [pos-cli Changelog].
• Referencing GraphQL files
• Previously, the example file app/graphql/my_diectory/my_query.graphql was invokable via {% graphql res = 'my_query' %}. It was the only resource which behaved like this. Moreover, due to the uniqueness constraint on name, it was often leading to structure like graphql/module_a/module_a_create.graphql and graphql/module_b/module_b_create.graphql instead of graphql/module_a/create.graphql and graphql/module_b/create.graphql.
• After the change, the expected way to invoke it is {% graphql res = 'my_directory/my_query' %}. For backwards compatibility, the previous way still works, however a deprecation log is generated. For this particular example, it would look like this:
• `DeprecationWarning: Finding GraphQL query/mutation by only name is deprecated, use full path instead.
• Replace my_query with my_directory/my_query
• `

New Feature

• Possibility to duplicate Instance 1-1 from any stack to any stack. It means, you can copy a site from staging to production, production Sydney to production London. It even allows you to migrate a site from the AWS Stack into the Google Cloud Stack. Includes all admin resources like forms, GraphQL queries, data like models, users, user profiles and user uploads - assets, images, attachments. Please watch our [Instance Copy demo on Town Hall #77] for details.
• Ability to filter GraphQL Query users by related_model
• This example query will find all company owners (users) whose company's (which is a model in his example) property "codename" is either "ES" or "FI":
• `query {
• users(
• per_page: 10
• filter: {
• related_models: {
• join: { join_on_property: "id" foreign_property: "company_owner_id" }
• filter: {
• model_schema_name: { value: "company" }
• properties: [{ name: "codename" value_in: ["ES", "FI"] }]
• }
• }
• }
• ) {
• results {
• id
• email
• companies: related_models(join_on_property: "id", foreign_property: "company_owner_id" model_schema_name: "company"){
• codename: property(name: "codename")
• }
• }
• }
• }
• `
• ability to filter GraphQL Query users by related_users
• This example query will find all users whose boss's first name is John:
• `query {
• users(
• per_page: 10
• filter: {
• related_users: {
• join: { join_on_property: "boss_id" foreign_property: "id" }
• filter: {
• first_name: { value: "John" }
• }
• }
• }
• ) {
• results {
• external_id
• email
• boss: related_users(join_on_property: "boss_id", foreign_property: "id") {
• external_id
• first_name
• email
• }
• }
• }
• }
• `

Bug Fix

• Uniqueness validation for user property
• Edge cases when content_updated_at was always updated, even though content has not been directly changed
• {% assign = %} will now throw syntax error

Improvement

• asset_url will always render a full path to file hosted in CDN, even if it does not exist in the manifest

Bug Fix

• static_cache expire config in Page will cache Page for given time
• match filter error handling for invalid expression
• presign url - fix for path with spaces and other special characters
• deprecated current_user will return the same hash as recommended context.current_user to avoid unexpected errors
• asset_url will correctly decode the name before looking it up in the manifest
• removed legacy routes to correctly display 404 if the Page does not exist (internal error was returned instead for some edge cases like /webhooks)

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