Create an AclTag token with a bound ACL_TAG_NAME_ASYNC_TOKEN which resolves to a Behavior Subject. Inject this behaviour subject and forward the tag name to the Acl Tag.

Created because the directive wasn't able to inject itself like it's working with usual components

providers: [ createAsyncAclTagProviders() ]

The version of dependencies in the following method have to be maintained manually. They are not part of the TALY's workspace so they won't get automatically updated.

Convert Dynamic Form configurations to Building Block configurations.

Apply extra transformations to a journey to be used internally.

Support

Helper to get proper access to a control and it's parent group. We can't use form.addControl('some.path', control) as this would use 'some.path' as the key and not access the group some and the the control path there.

This helper does a proper traversal and returns the group and the matching control key (last part of the path) which can the be used to access group.addControl and group.removeControl

Remove or Add a form control by it's control key. The control must be available on the given form, will be cached through the closure

Apply validators from the given validationMap to the given control if it's a "new control" (i.e. if it has not had validators applied). If the given control is a form array or form group it will recursively call itself for all child controls.

The controlPath parameter is used to manage the recursion and is expected to be empty in the initial call.

whether a new control has been taken care of

Apply a validation configuration to a form group. For each accepted validation (as we only support a subset of validations) we will create a configuration entry (ValidationConfig) which is used to find the control & apply the validations.

Validation Error Message are independent of the form control. The form control only knows about the validation name that goes wrong. The actual processing of those needs to happen in the template. For this purpose we return the entire map of ValidationConfig objects to easily access the errorMessages available in there.

This function has to be called on destruction of the form/component that called applyValidationConfig() in the first place. It ensures that the obsolete form is removed from the cache and that all active subscriptions are being shut down. If it is not called, the component won't be outkast from memory and will stay forever, ever, forever, ever...

Ensure that we don't have duplicates in the given list of validations.

Returns the sync and async validators for a form control path. Will return empty arrays if the given control path has no validators configured.

tuple with array of sync validators and array of async validators

Pass in the config from a page config to retrieve a populated Map of applicable ValidationConfig[] per control id.

Very simplistic factory that receives a configuration directly from the pages configuration (e.g. { "required": true}) and returns the matching validators from Angular or from the configured plugins.

This will be the single place where we can handle validations beyond required including params etc (like min/max).

Given a Configuration Item with a type return the matching Validator. This will include the error message from the given configuration or takes a default value which will be part of the application translation.

Aggregates the split journey configuration into a classic journey configuration.

The aggregated (classic) journey configuration.

Extracts duplicate values from an array.

An array containing the unique duplicate values.

Loads the split journey configuration from a folder.

The split journey configuration, loaded in memory.

throws an error if the contents of the given file don't match the given schema.

throws an error if the given multi-tenant journey config doesn't match the JSON schemas

throws an error if the given split journey config doesn't match the JSON schemas

wrap the lodash set function (imported as setObject) with a better name to help reading the context.

Transform a list of resources into a stream of StaticResourceList. The recipe is: extract the static data and add the latest values from all given pfe queries The resulting object can then be passed to a Building Block's setResource method.

Given a resource list return a map of PFE Queries where the key is the future key in the resource object being passed to setResources() and the value is retrieved by the pfe store expression in the PFE Query.

Extract all static values from a resource list

Take a list of PFEResourceQueries and transform them into a single map containing all mapped values from the store

We need to deep merge resource objects and a spread operator will fail this task as nested keys with the same name are not merged (it's shallow)

a = { nested : { valueA: 1}} b = { nested : { valueB: 2}} result = { nested : { valueA: 1, valueB: 2}}

the joined path, generates list-like paths for numeric path pieces

Check if it's a form group and use a TS type guard to let TS know that it is indeed a FormGroup in the control flow

walkFormGroup

comment-json stores the read comments in non-enumerable properties. These properties are ignored by both structuredClone as well as lodash's cloneDeep. This function uses comment-json's own stringify and parse to deep clone an object with these non-enumerable comment properties.

Find all suitable folders that contain a Building Block. A Building needs to be an Angular component, with a Markdown Files and Module. All with the same name

Create a small stat report about the given folder. Check if all required files for a Building Block do exist and return details of the check for a later analysis/logging to provide some verbose output.

Find and collect all Building Blocks with a given example state and store it inside a map to further access.

Take a collection of Building Block IDs and example state strings and render them as a list of variable assignments to output it directly into a component template.

const myBbExampleState = {foo: "bar"}

Find all suitable folders that contain a Plugin. A Plugin needs to be an Injectable, with a Markdown Files and Module. All with the same name

Create a small stat report about the given folder. Check if all required files for a Plugin do exist and return details of the check for a later analysis/logging to provide some verbose output.

collects building block metadata and the used libraries from a pages.json configuration.

Utility function to be used inside of Building blocks to provide possibility compare dataOption object by value in the dropdowns.

Given a list of AclControlItem use a factory to create streams for each control which will adjust depending on a given acl key subscription. The entire list is merged to listen for future changes afterwards.

And here our custom code follows:

Given a sourceFolder, copy its entire content into the given tree at destFolder.

helper via https://stackoverflow.com/questions/49102724/angular-5-copy-to-clipboard

determines if rule "rule" is relevant for path "aclPath" and state "state" does not take the rule's condition into account

Maintain a stream of added & removed Building Block instances so we can either cleanup removed Building Blocks or add missingFacades

Create a stream of WAITING or COMPLETE signals depending on the status of all Building Block currently on the page.

Create a control list from all form controls in a form group including nested ones.

Create a manual mapping between form controls and acl keys. The resulting array of AclControlItems can directly be consumed by bindControlList

Only map given explicit map of acl keys and control paths

support utility to enrich a given page array with previous and next pages pointers

create a single pfe navigation config node, with minimal content to point to next page

Forward all calls to a given AclEvaluationInterface and prefix the argument, which is a aclPath with the prefix given through the prefixResolver callback.

Prefix the acl evaluation with an ACL Tag. You can pass in for example a root AclService or directly an AclEngine and prefix all queries with the given prefix value

Prefix the acl evaluation with an ACL Tag. You can pass in for example a root AclService or directly an AclEngine and prefix all queries with the given acl tag's key.