Syntax & Compatibility Mode

Digital Script is ES5 plus the Rhino forms B2C Commerce runs. Newer syntax depends on the compatibility mode of the code version, and the plugin marks what that mode can't run, with a fix to the older form

Unsupported syntaxES5 fixesRhino forms

STstorefrontSandbox 01version2

Labels.ds

1importPackage(dw.util);

2

3function labels(items : List) : Array {

4 if (!items?.size()) return [];

5 var out = [];

6 for (var item of items) {

7 out.push(`${item.name}: ${item.price}`);

8 }

9 return out.map((label) => label.trim());

10}

No B2C compatibility mode supports optional chaining

Compatibility mode 19.10 does not support for..of loops (21.2 or later)Convert to 'for each' loop⌥⇧↩

Compatibility mode 19.10 does not support template literals (22.7 or later)Convert to string concatenation⌥⇧↩

Compatibility mode 19.10 does not support arrow functions (21.2 or later)Convert to function expression⌥⇧↩

storefrontapp_customcartridgescriptsutilLabels.dsGlobal scopeLFUTF-8

Rhino forms

These parse as code in .ds files and server .js files:

var mode = response.fraud.@mode, isDefault = node.@['default'];
var all = xml.*, items = xml..item, deep = xml..@id, qualified = xml.ns::name;
delete attributes.item.(@id == 'y')[0];

default xml namespace = new Namespace('http://www.demandware.com/xml/impex/catalog/2006-10-31');

Templates parse E4X members in ${...} and <isscript> too, but not XML literals. Unicode format characters such as a zero-width space count as whitespace, as Rhino reads them

Expression closures, legacy generators, let blocks and array comprehensions don't parse yet

Rhino checks

To move a loop to ES2015, use the Convert to 'for...of' loop intention, see Intentions

Compatibility mode

B2C Commerce runs each code version in a compatibility mode, set in Business Manager › Administration › Site Development › Code Deployment. Modes before 21.2 run Rhino 1.7R5, 21.2 runs Rhino 1.7.13 and 22.7 runs Rhino 1.7.14

No mode runs classes, generator methods, default values, rest parameters, spread syntax, computed property names, async functions, object rest and spread, optional chaining, the ?? operator or logical assignment. Every mode runs let, const, array destructuring, for each, getters and setters, and type annotations, so this check never reports them. 'let' or 'const' in server code still asks for var, see let and const

Where the mode comes from

A new mode applies without a restart, in every open script and template

Unsupported syntax

Script syntax the compatibility mode does not support is an error, free, and works while the IDE indexes. It names the mode that runs the syntax:

• Compatibility mode 19.10 does not support arrow functions (21.2 or later)
• No B2C compatibility mode supports optional chaining

importPackage(dw.util);

function labels(items : List) : Array {
    var out = [];
    for (var item of items) {
        out.push(`${item.name}: ${item.price}`);
    }
    return out.map((label) => label.trim());
}

importPackage(dw.util);

function labels(items : List) : Array {
    var out = [];
    for each (var item in items) {
        out.push(item.name + ': ' + item.price);
    }
    return out.map(function (label) { return label.trim(); });
}

Templates get the same check for ${...} and <isscript>, see ISML inspections

IDE suggestions that follow the mode

The IDE's own suggestions that write syntax the mode can't run are hidden in Digital Script: arrow functions, template literals, for...of loops, shorthand properties, classes, async functions and object destructuring. With Not set, a form some mode runs counts as runnable. Convert to let and Convert to const are hidden too while 'let' or 'const' in server code runs, which needs a license and is on by default. Without it, only Convert to const is hidden, and only where the const would run differently on Rhino: in a loop, or beside another declaration of the name. Client .js files keep every suggestion

Intentions that turn require into ES import or module.exports into export are hidden in Digital Script, since the server runs neither

Related