Skip to main content

Customizations

As mentioned before there are 2 ways to add custom code to an application:

  • Insert code in custom anchors.
  • Add a custom file to one of the ext directories.

For the angular-expanders a new technique of handling ext folders has been implemented. Physical ext and gen folders are no longer necessary, but a manifest file is used to keep track of which artifacts have been expanded. This makes it possible to use every folder as an ext folder and have an ext file live next to a gen file. However, in order to keep a clear structure throughout all expanded Angular projects – as in our JEE stack – not every folder acts as an ext folder. The following decisions have been made:

  • The root folder acts as an ext folder for configuration files. Meaning, files can be added, but no folders with files. It is only harvests 1 level deep.
  • Assets is an ext folder.
  • The subfolders of styles are ext folders.
  • The subfolders of core, shared and feature modules act as an ext folder. This means components, services, features, etc.

Every folder mentioned above except for root allows harvest of subfolders and more layers deep if wanted. However, keep in mind that a flatter structure is preferred in Angular front-end projects.