Skip to content

Version 0.19.1

Compare
Choose a tag to compare
@Codeneos Codeneos released this 04 Apr 08:43

0.19.1 (2023-04-03)

Bug Fixes

  • activate integration procedures using remote APEX (3f79191)
  • add unit test for proxy transformer (4a3d1c9)
  • additional validation on OmniScript templates to avoid linking templates that are not strings (0d66200)
  • before and after deploy specs do no respect record filter (299eb4c)
  • bug in schema normalization not working properly for arrays (44cec8f)
  • bulk queriy results do not include related object details (6fd7e4f)
  • bulkJob compiler error due to info being readonly type (c32f014)
  • calculateHash does incorrectly references this from a static context (0575fd3)
  • compile issue due to breaking change in SfdxConnectionProvider arguments (ac3efc8)
  • connection hook fails to attach due to connection not always being a promise (2ef12cb)
  • datapack deployment tries to delete matching key records that can be updated in exceptional cases (43b1ce4)
  • datapack explorer does not list certain datapacks due to query parser error (d031866)
  • datapackLookupService does not update the namespace of the filter when comparing field values causing a bugcheck (826205f)
  • definition builder for OmniScripts concatenates templates in a different order then APEX activation. (5abf833)
  • deploy command does not await init on super class (97596a1)
  • deployed OmniScript using local activation does not get updated to activated after deploying the definition and LWC (4051b81)
  • display warning for omniscript datapacks without elements instead of an error (62f2398)
  • do not dump old and new script definitions during activation (81f9a17)
  • do not exit when async interator has 0 results (71ed265)
  • drop uuid package in favor of browser and node native randomUUID from node:ctypto (78e954c)
  • encodeRFC3986URI does not encode & character causing queries with an & to fail (029b607)
  • ensure that script activation does not delete the old definitions before ensuring the new version can be activated (only when activating a new version) (0e6631a)
  • exclude datapacks that are not loaded properly due to spec-function errors from the deployment and properly log and attach spec function errors to the respective datapack that causes them (c4c7fb1)
  • fix QueryService test mocks query operation instead of underlying transport (5e33d7b)
  • fix several script generation errors (eff0ef0)
  • getErrorMessage does not use defaults when set (00868ec)
  • incorrectly mapping version to sub type for script definition generation (e6ff15a)
  • IPs with single elements crashed updateElementOrder due to that expecting elements to always be an array (ae66a4a)
  • lookup service does not report script name/id in lookup error (8021d97)
  • LWC compiler throws error when the tooling record is not updated as Salesforce returns a 204 status code with no body (64e4eaf)
  • LWC enabled scripts with embedded scripts did not render elements inside of blocks (d0c9b9c)
  • mapGetOrCreate does not play nice with sync-initializers (d06d5cf)
  • normalizeSalesforceName transforms uppercase acronyms to xML instead of xml (8f3df44)
  • only run tests for test and spec files in tests folder (65fb3a9)
  • only update order and level when not set in the datapack. (a26f6e3)
  • QueryService resolves namespace from base container (e07b578)
  • re-ordering of elements should start counting at 1 for element order instead of 0 (1bdc38c)
  • relationship incorrectly cast to arrays in iterator (e9a5e03)
  • rename sass folder to scss to avoid conflicts with sass nodejs module (41dd5cf)
  • retrieveMetadata command does not request zip file causing no files from being refreshed (e137dfd)
  • script gen crashed on invalid picklist configuration for a choice element (89ec371)
  • toolingApiSchemaAccess transforms nested results which are already processed by query2 (825a0b6)
  • transform proxy does not transform array methods properly (e7be106)
  • UI layouts are incorrectly linked to UI templates (7b949fc)
  • update order and level of OmniScript elements before deployment (issue #396) (c9c08f1)
  • use getSObjectType in query cache to avoid errors when caching complex queries not yet supported by the parser (57aea51)
  • vlocode ignores tooling API flag and always uses Metadata API for uploading LWC OmniScrips (707b6bf)
  • when building multiple definitions they re-use the same objects instead of deepCloning them (24fe045) ### Features
  • activate scripts in accordance to their dependency graph (1295364)
  • add new activation command to activate OmniScripts and deploy LWC components already deployed in the org. (c045bca)
  • add new mapBy function to easily map arrays by key (23083b6)
  • add support for reactivating dependent scripts (2a8a42c)
  • always regenerate the LWC id when building the script definitions (2f57fc0)
  • automatically reactivate dependent scripts (c92c5ea)
  • change getErrorMessage signature to accept options and allow default options to be set easily (f1e8d46)
  • expose --continue-on-error for vlocode CLI deployment command (dcc014a)
  • expose job info on bulk/bulkJob.ts as readonly object from the job (0b777be)
  • improve query parser correctness by enforcing keyword order on SOQL syntax parser (04dc796)
  • include logging of queries in debug mode (296395a)
  • introduce new uniform query API for data and tooling objects; update query service to use new query API. (775ca10)
  • local OmniScript activation now updates the isActive flag to true and deactivates the old active version of the same script (08092e4)
  • open LWC OmniScripts in LWC editor and classic in Angular designer (e016d3f)
  • report stack trace for datapack loading errors during datapack deployment while debugging (b282180)
  • support correctly parsing datapacks that are not in a parent folder (ae261c2)
  • support local OmniScript definition generation instead of using remote APEX. This speeds up OmniScript activation and avoids govern limit issue when activating large scripts. (5bbd304)
  • support more datapack types in datapack explorer (3a19411)
  • support more lookup configurations for OmniScripts (6ea32b4)
  • support unary operators, with condition and braces for query parsing and generation (87d56c8)
  • support unlimited re-usable OmniScript embedding; allows more then 1 level deep embedding of scripts (bb23f67)
  • switch from sass.js to sass-dart for scss compilation; sass.js is not unmaintained and not being updated anymore (807e45c)
  • update calculateHash to also work on strings for convenience (b5fd2c1)