Sign In

ampscript-data

Package Overview
Dependencies
Maintainers
1
Versions
23
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

ampscript-data - npm Package Compare versions

Comparing version
3.2.0
to
3.3.0
+1
-1
package.json
{
"name": "ampscript-data",
"version": "3.2.0",
"version": "3.3.0",
"description": "Canonical AMPscript function catalog, keywords, and personalization strings for SFMC tooling",

@@ -5,0 +5,0 @@ "type": "module",

@@ -58,9 +58,21 @@ # ampscript-data

console.log(fn.guideUrl); // URL to ampscript.guide reference page
console.log(fn.sfmcGuideUrl); // URL to our own sfmc.guide reference page (only when published)
console.log(fn.mcnSince); // API version when MCN support was added (null = MCE only)
console.log(fn.mcnNotes); // behavioral differences on MCN (null = none)
console.log(fn.handlebarsEquivalent); // MCN Handlebars helper name, or null when none exists
console.log(fn.mcnHandlebarsGap); // true when MCN-supported but no Handlebars helper yet
console.log(fn.handlebarsExact); // true = drop-in replacement, false = same job, different call shape
}
```
#### Optional: `sfmcGuideUrl`
`docUrl` and `guideUrl` point at third-party documentation and are set for (almost) every function. `sfmcGuideUrl` is different: it links to our own published reference page and only exists once that page has been written, which happens at the end of a runtime verification sweep. It is therefore a reliable marker for "this function has a proven, self-hosted reference page":
```js
const entry = functionLookup.get('add');
entry.sfmcGuideUrl; // 'https://sfmc.guide/engagement/ampscript/functions/add/'
```
The URL is always `https://sfmc.guide/engagement/ampscript/functions/<lowercase-name>/`, and an entry carrying it is always `isConfirmed: true`.
#### Optional: `validArities`

@@ -176,3 +188,3 @@

Each `FunctionEntry` has two MCN fields:
Each `FunctionEntry` has these MCN fields:

@@ -183,6 +195,6 @@ | Field | Type | Description |

| `mcnNotes` | `string \| null` | Behavioral differences on MCN vs MCE; `null` means no known differences |
| `handlebarsEquivalent` | `string \| null` | Name of the MCN Handlebars helper that replaces this function (e.g. `'add'`); `null` when no direct helper exists |
| `mcnHandlebarsGap` | `boolean` | `true` when the function is documented as MCN-supported but currently has no working Handlebars helper (runtime gap) |
| `handlebarsEquivalent` | `string \| null` | Name of the MCN Handlebars helper that replaces this function (e.g. `'add'`); `null` when no counterpart exists |
| `handlebarsExact` | `boolean` | Only meaningful when `handlebarsEquivalent` is set: `true` = argument-for-argument drop-in, `false` = same job but different call shape (converter emits a hint) |
`handlebarsEquivalent` and `mcnHandlebarsGap` drive AMPscript ↔ Handlebars conversion tooling. When `mcnHandlebarsGap` is `true`, `handlebarsEquivalent` is always `null` — the function cannot yet be expressed in MCN Handlebars and needs a manual rewrite.
`handlebarsEquivalent` and `handlebarsExact` drive AMPscript ↔ Handlebars conversion tooling. When `handlebarsExact` is `false`, the helper does the same job but with a different call shape, so conversion emits a hint for a human to finish rather than a mechanical substitution.

@@ -189,0 +201,0 @@ Three helper functions are exported for programmatic MCN checks:

Sorry, the diff of this file is too big to display