Builder changelog

This page contains the changelog for the builder. It is updated with each new release of the builder.

1.55.0

  • GS-28342 Adds new ‘automat’ based loading capability, this allows wasm applications to be hosted on automat pages instead on the dist server itself
  • Adds new tools helper .Tools.HasErrors that can used to check if the tools functions produced any errors during execution

1.54.6 - 1.54.14

  • GS-25581 Updated targeted loads on services. Same page targets will no longer force the full re-render. Extended functionality to forms with actions.
  • GS-26908 Fixed a load order issue in dev builds that was overwriting data of templates when it was loaded in a specific order
  • GS-27016 Adds support for v2 run dynamic calls (not enabled yet as it requires server to be updated to 1.340.151)
  • Fixed an issue where service run dynamic calls would fail with nil map pointer error
  • Changed service build local TLS resolver
  • Fixed an issue where it was not possible to remove existing public builds
  • Added windows arm64 to the allowed OS and architecture combinations for builds
  • GS-27207 imported file helpers for functions
  • GS-27148 fixed an issue where the parameter in wasm builds were loaded incorrectly versus the server and service builds
  • Fixed an issue where parameter arrays were no longer working in wasm
  • Fixed an issue where file inputs were actually not usable in wasm functions
  • GS-27270 Added an option to defer function call inside func templates (only one function can be deferred)
  • GS-27273 Added .Array method to the jsonObj. Returns JSON array as []map[string]interface{}. JSON content must be an array.
  • GS-27384 Replaced unsafe string conversions with the regular one, as it was causing corruted references when it was accessing fastHTTP bytes (as this is reused)

1.54.5

  • GS-25581 Updated targeted loads on services. Same page targets will no longer force the full re-render. Extended functionality to forms with actions.
  • GS-26908 Fixed a load order issue in dev builds that was overwriting data of templates when it was loaded in a specific order

1.54.4

  • App user model in session now includees the loginMethod field. The session will also include the app accesses and warehouse accesses in the session. This is also filled when using app user with the back office auth driver.
  • GS-25581 Service builds: a nodes with targeted loads will no longer skip the main navigation
  • GS-25581 Service builds: data passes from the targeted loads from functions will now work similar to wasm
  • GS-26708 Dev builds: Configuration is now validated before it get loaded
  • GS-26708 Dev builds: Improved load and reload operation to be more lightweight
  • GS-26871 Added stale write guard for targeted loads elements to prevent old calls that might take time to complete from overwriting newer calls that already updated the content

1.54.3

  • Adjusted .Tools.GetMenuStructure to return the same level data as on the server

1.54.1 / 1.54.2

  • GS-26476 Adds support for InventoryApi dynamic api integration
  • GS-26490 CallTemplate calls will no longer append the ? character to the url without the query parameters or when the path input already contains one
  • GS-26490 The autofocus functionality of the server can now be mimicked by adding the attribute data-wsm-refocus on the body node of the current page
  • Added ApiCommandBroker to supported internal dynamic api’s
  • GS-25581 Improved service build targeted loads functionality so it supports detached forms from buttons

1.54.0

  • Local development build related updates

1.53.1, 1.53.2

  • Fixed an issue where template matching logic was case-sensitive from the default template link, causing it to fail on index as the index is always lower case
  • Various maintenance updates

1.53.0

  • GS-26283 Updated dataLoad to make automatic object to gjson conversions (imorted from server behaviour)
  • GS-26283 Added FDR api integration to wasm
  • GS-26283 Adds support for .Data.Files
  • Added automatic menu structure translation to service/wasm builds
  • GS-26284 Adds new optional 4th parameter to target load from functions .Tools.AddLoadTarget "wtl-table-b-page" "#table-b" "afterx" (mkMap "key" "val"). Contents are readable on that page from .Data.Parameters
  • Improved targeted load script for service builds, it will now also parse load parameters from form elements

1.52.2

  • Configuration update. No functional changes.

1.52.1

  • Fixed an issue where script tags would be purged of extra attribute tags and its type always adjusted to text/javascript

1.51.0 and 1.52.0

  • GS-25717 Service and app routes now support app routes navigation. It also supports navigation by template route alone if the app route is not provided.
  • GS-25581 Adds targeted loads fallback capability to service builds, so application builds would not lose functionality when built there. This is currently experimental and will likely receive further changes for its behaviour.
  • Adds helpers to be available dtSince and indexOfStringSlice
  • Adds tools helper to be available {{ .Tools.GetStaticNavPath "my-page" }}
  • GS-25845 Adjusted toTitle behaviour to match that of the server
  • Added new tools helper to list all applications and v2 modules that have been added to the build {{ .Tools.ListV2Modules }}
  • Build flow improvements: fixed an issue where the new flow would reach command line length limits on large applications.
  • GS-25834 Adds new tools helpers (for use in functions only) for B2B authentication (B2BLogin, B2BLogout, B2BLoginRegister, B2BRequestPasswordReset and B2BConfirmPasswordReset)
    • All take in the same json instruction as the corresponding calls on the api {{ .Tools.B2BLogin {“username”: “”, “password”: “”, “authDriver”: “password”} }}. The template field is filled automatically.
  • GS-25894 Adds new helpers to generate local bcrypt hashes and verify them {{ bcryptHash "my-password" }} and {{ bcryptVerify "my-password" "the-hash" }}
  • GS-25232 RunQueryV2 is now supported on service and wasm builds
  • Adds support for ApiLogFiles api in integrated dynamic API’s
  • GS-25602 Adds an option to render js scripts as per-template scripts (same as the server and service does) instead of the single blob. This is experimental and will likely break applications that have already been built with the default single blob setting.