Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Info
titleWIP

This page is a work in progress

...

Already exists, fetching and processing the configuration JSON works just the same as any other data JSON.

Examples

Several modules already use "Distributed Configuration via Path", see these examples that show CRUD configuration APIs:

Module, type of configurationPath

mod-inventory/inventory-config

/inventory/config

mod-invoice/batch-voucher-export-configuration

/batch-voucher/export-configurations

mod-invoice-storage/batch-voucher-export-configuration

/batch-voucher-storage/export-configurations

mod-orders/configuration

/orders/configuration

mod-orders-storage/configuration

/orders-storage/configuration

mod-event-config/event_config

/eventConfig

mod-data-import-converter-storage/form-configs-storage

/converter-storage/forms/configs

...

  • Every implementation of configuration is different, meaning separate implementations and separate client code is needed. However, this code can be extracted into a method for re-use, and the method calls differ by parameter only. The same applies to the multiple interface solution and the namespace solution.
  • Each module has its own configuration interface resulting in more paperwork when comparing to the existing mod-configuration solution; the multiple interface solution and the namespace solution also require interface paperwork for each module.