To prevent constant forking or cloning of the exporters to change specific behaviors, each package can define a specific set of configuration properties that are available to you when you install the exporter.
This configuration can, for example, allow you to disable the generation of specific files, maybe provide prefixes for generated classes, and so on - what configuration is exposed is decided by the exporter developer.
Accessing Exporter Configuration
To access the exporter configuration, first, make sure you have installed the exporter in your workspace. Once that is done, you will be able to access the exporter settings on the cloud.
Exporter configuration allows you to quickly re-defined behaviors without the need to clone it
Note that immediately after you change the configuration, it will affect the behavior of all the places where this exporter is used - be it in manual builds, through automated code delivery, or even in VSCode. This is done so the behavior is always consistent across all the teams.
There are three types of configuration you can encounter in each exporter:
String values , usually used for things like class names, prefixes, comments
Numeric values, usually used for things like limits, paging, visual properties
Boolean values, usually used to enable or disable certain behaviors
Not only the configuration can change the behavior, but also the structure of the resulting output because boolean values can also be used to define what files should be generated and what not.
Before configuration is exposed to the user, authors must declare what information they want to be changeable. This is done through the declaration of this configuration inside exporter packages.