Change Log

New Features

• Added CSS variables for Insites Theme
• Added Cache-Control with max-age of 1 year to components and assets
   

Improvements

• Separated styles from the components for theming and caching
• Updated event names to avoid native DOM event conflicts
• Updated APIs to be asynchronous to avoid race conditions
• Updated ins-base-table to ins-table
• Updated components to include third party libraries
• Updated CDN to serve gzipped version

New Feature

• [redirect_to] - a new tag to do server-side redirection via liquid

Bug Fix

• fix value_in for array property
• error handling when Email uses non existent layout
• indexing geojson user property
• pos-cli pull includes now asset manifest, which then can be imported via pos-cli deploy
• pos-cli import will not return an error when empty zip is provided as an argument

New Feature

• Liquid engine upgrade; adds new liquid and echo tags
• data_export mutation which triggers the export task similarly to pos-cli data export, with the possibility of extra filtering and scoping for users and models
• possibility of invalidating authorization tokens used by pos-cli via the Partner Portal

Bug Fix

• graphql tag was not overwritten properly when variable was used multiple times inline
• error handling of unknown resource type in include_form tag
• error handling for notifications
• error handling when the form tag is used outside of the include_form scope
• remove unnecessary noise when pulling schema via pos-cli pull
• error handling when invalid time zone is provided to time filters

New Feature

• [Work in progress] upgrade Liquid engine to support functions like syntax, add new built-in tags and filters

Bug Fix

• fix rendering a Page with the DELETE method submitting via the form tag

New Feature

• added the admin_asset_delete mutation which deletes physical files from the storage

Bug Fix

• deprecated unnecessary filters - asset_path, fetch, nl2br
• Instance edit via Partner Portal API

Improvement

• API Call Notification error handling for various scenarios, for example, target endpoint error responses (Timeout, SSL error, etc.),
• Deprecated the format property of API Call Notification, which was not used for anything other than validation
• No need for {% if form %}...{% endif %} in Form's default_payload anymore - disabled Liquid processing during validating whether default_payload is a valid JSON if it includes any Liquid Tag. This also avoids unknowingly invoking a code during sync/deploy.
• Error message when trying to use related_model and using property in join_on_property of type array
• Error messages for admin_mutation_* mutation like physical file path already taken, Liquid syntax error, etc.

Bug Fix

• Error when null value is provided as request_headers for API Call Notification

Improvement

• improved error messages in multiple places when invalid model_schema_name is provided (for example, forms, model_create mutation, etc.)
• added information about max limit for fetching related_models/related_users to 10.000
• error handling for sum_array when invalid argument is provided
• validation for admin_* mutations to provide proper information about duplicated physical file path

New Feature

• DEPRECATION added layout to Page and EmailNotification and deprecated layout_name for Page and layout_path for EmailNotification
• added email validator

Improvement

• error message for not sending Email Notification
• to_mobile_number filter will add + if the phone starts with country code
• map filter implementation and its description
• added case insensitive modifier and multiline option to regex_matches and matches filters
• DEPRECATION rename headers to request_headers in API call notifications to avoid ambiguity and be consistent with response_headers in Pages
• handling different formats than html for error pages triggered by Authorization Policy
• error message when empty zip file is provided as an input to the new import script
• error message when a hash was provided as a query name to the graphql tag
• error message when empty hash was provided as an argument to the related_models argument in GraphQL query
• error message when trying to fetch the model_schema_name for the models GraphQL query when both were soft deleted

New Feature

• Added request_allowed flag to Form to control whether a form will be available as an endpoint (which is deprecated). If false, the form will be usable only through GraphQL mutation. Default is true.

Bug Fix

• overwriting email and password validation messages
• Authorization Policies sometimes were invoked twice
• Authorization Policies sometimes were returning the 200 status code instead of the one provided in http_status

Improvement

• namespace is now an optional attribute in the exports tag, previously it was mandatory
• value_int and value_boolean GraphQL arguments will work also with castable string data
• added property argument in the compact filter to be better compatible with the built-in Liquid implementation
• possibility to sort by property defined in user.yml in the users GraphQL query
• error handling of the new import CSV mechanism

Bug Fix

• fixed edge case scenario when invalid argument was provided in the parse_json filter
• fixed edge case scenario when resource was set to Model in Form

New Feature

• [Beta] new property type upload to replace custom_images and custom_attachments. It is still work in progress and the interface might change. Final documentation to be provided within the next few weeks.
• added sms_send GraphQL mutation to work similarly to email_send and api_call_send

Bug Fix

• gracefully handle error when admin_* mutation was invoked with name, but without required physical_file_path
• pos-cli logs sometimes included unnecessary internal error message
• added model_name as a restricted property name
• added graceful handling of a scenario of uploading a file with a name that's too long
• added better handling of invalid regpexp in regex_matches filter
• fix descriptions of multiple GraphQL mutations
• fix documentation example of raw_escape_string filter
• fix edge case scenario when integer is provided as a path name for the include tag
• {% form %}{% endform %} was rendering nothing instead of the form HTML tag
• fixed edge case scenario when invalid arguments were provided to precision argument in the time_diff filter
• fixed edge case scenario when invalid arguments were provided to the format_number filter