Help type to include all the possible types that can have an array

A single condition. Includes the legacy and new conditions.

The legacy ExpressionCondition and ConditionAdvanced, including also the PfeBaseCondition[]

Conditions that are available by default

Strict mode in typescript also activates the strictFunctionTypes. See: https://www.typescriptlang.org/docs/handbook/release-notes/typescript-2-6.html

This means, that it turns functions as parameters from bivariant (contravariant or covariant = subtypes allowed in the parameters of the functions) to contravariant (not allowed).

As this does not apply to methods, the BivariantCallbackFunction type can be used to disable the contravariance for functions that are used as parameters.

A concrete example why this workaround was introduced: The PfeActionFunction expects a function with this signature: (actionConfig: PfeBaseActionConfig) => Promise<void | boolean> A concrete implementation of a PfeActionFunction is going to use a more specific derived type for the PfeBaseActionConfig. With contravariance, this is not allowed because: If that PfeActionFunction would be called with the config of another PfeActionFunction, that also extends the PfeBaseActionConfig, but has other attributes, the original function would try to access its expected attributes that are not available in this case.

As it is certain that this case does not happen, this workaround is used to keep the bivariant behavior.

A more hands on example about this, can be found here: https://github.developer.allianz.io/tobias-siebert/typescript-strictfunctiontypes-covariance-and-contravariance

This file contains the data models that are used for the json schemas that are shipped with the PFE.

typescript-json-schema is currently not able to handle default generics:

Handles a serviceActivator call error.

Text that can contain placeholders in the form: %jsonPath%$.variableFromTheState%jsonPath%

The service activator configs.

Unique ID of a page.

These are the integrated default actions. Should be used as a basis for custom extensions in apps

Actions have to implement this function.

An action can return a boolean result to indicate if further execution should be stopped. For example, this applies to a navigation that triggers an action. If no boolean is returned, a positive (true) response is assumed.

This works in a similar fashion as the Angular route guards with the difference that actions are not executed in parallel. But: The break flag in the action config has to be set to true, to prevent further actions from being executed.

If an exception is thrown by this function, the execution of the actions is aborted. The function itself is responsible to handle things like a redirection to an error page, etc...

Extends the Angular Route and ensures that either loadChildren or loadComponent is set (but never both).