zweidenker / cinic Goto Github PK

When applying a given configuration, associated steps to execute are collected in an undetermined order from pragmas present in the pharo image.
Moreover, only top level sections are currently considered.

Instead, we could ensure that configuration steps are executed in the same order as the sections definition order in the file.
And this for all sections in the file (top-level or inner)

Classes and pragmas names are still using the "Configuration" prefix.
Which is quite generic and open to potential name conflict.
We could now use the "cinic" prefix instead

provide a dedicated pharo command line option to apply a given configuration at image start-up.
Something like:

--cinic myconfig.json