Extensions overview

All customisation funnels through a single config type, INgxViewBuilderExtensionsConfig, registered either at bootstrap or at runtime.

Registering

At bootstrap (recommended):

import { provideNgxViewBuilderExtensions } from '@ngxviewbuilder/runtime';

providers: [
  provideNgxViewBuilderExtensions({
    elements: [...],
    expressionFunctions: [...],
    svgIcons: {...},
  }),
]

The provider also accepts a factory (sync or async), which helps when the config comes from an API:

provideNgxViewBuilderExtensions(async () => {
  const cfg = await fetch('/api/builder-config').then((r) => r.json());
  return { runtimeVariableContext: cfg.context, svgIcons: cfg.icons };
}),

At runtime:

api.registerExtensions(config);
await api.registerExtensionsAsync(config);   // resolves icon directories etc.

Multiple provideNgxViewBuilderExtensions(...) calls compose; plugins use the same mechanism.

What the config can contain

Key	Registers	Details
elements	custom element types	Custom elements
elementGroups	new sidebar groups	id, label, icon, order
expressionFunctions	JEXL functions	Custom functions
globalProperties	properties added to every element	Custom properties
elementProperties	per-type property overrides/additions	Custom properties
svgIcons / svgIconDirectory / svgIconDirectories	icons by name / from asset folders	Icons
builderTabs	extra builder tabs	Building a plugin
featurePacks	bundles of tabs + capabilities	Building a plugin
runtimeVariables / runtimeVariableContext	variables for expressions	Runtime variables
uiDictionaries	builder UI translations	UI translations
triggers / rules / process / fragments	automation definitions	consumed by the automation plugins

Example: a project preset

provideNgxViewBuilderExtensions({
  elementGroups: [{ code: 'acme', label: 'ACME widgets', icon: 'acmeLogo', order: 10 }],
  elements: [acmeCardElement, acmeRatingElement],
  expressionFunctions: [
    { name: 'vatAmount', args: ['net'], description: 'Adds 21% VAT',
      example: 'vatAmount({netPrice})',
      handler: (net: unknown) => Number(net || 0) * 1.21 },
  ],
  globalProperties: {
    trackingId: { label: 'Tracking ID', type: 'text', category: 'general' },
  },
  svgIcons: { acmeLogo: '<svg ...>...</svg>' },
  runtimeVariableContext: { brand: 'acme' },
});

Everything a creator then sees (the ACME group, the elements, the vatAmount() function, the extra property) comes from this one object.