Skip to main content

Default Overrides

To make changes to expanded pages and styling we introduced two mechanisms to override the default behaviour powered by default anchors, namely:

  • Using a project specific expander to override the default behaviour.
  • Using model options to get custom anchors instead of the default behaviour.
tip

Overridable anchors are prefixed with branding or customization.

Project specific expander

In your project specific expander, you can add a feature called Customizations for example. On this feature you can add feature expanders for the potential overrides.

<feature xmlns="https://schemas.normalizedsystems.org/xsd/prime-core/2024/0/4/feature" name="Customizations">
<packageName>net.democritus.angular.customizations</packageName>
<condition>true</condition>
<type name="custom"/>
<expanderFeatures>
<expanderFeature>
<expander name="LayoutComponentHtmlExpander" packageName="net.democritus.angular.angularapp.core.components.layout"/>
</expanderFeature>
</expanderFeatures>
<options>
<feature.mapping.doNotInheritExpanderMapping/>
</options>
</feature>

Options

Option
angular.hasCustomBranding AngularApp

Indicates that icons, logo, images, colors need to be implemented custom and expands custom anchors to enable this.

<options>
<angular.hasCustomBranding/>
</options>
Option
angular.hasCustomHeaderContent AngularApp

Expands custom anchors instead of the default header implementation.

<options>
<angular.hasCustomHeaderContent/>
</options>
Option
angular.hasCustomTableRowActions DataView

Expands custom anchors instead of the default action implementation.

<options>
<angular.hasCustomTableRowActions/>
</options>