[Pharo-users] About magritte usage in pillar

Hi cyril I would like to discuss with you about the use of magritte in pillar for configuration. In particular I do not understand why accessors are not simply generated and stored as part of the code. It will avoid to have defaultExporters: treated as an unknow message. activate super activate. self optionAt: 'to' ifPresent: [ :subconf | configuration defaultExporters: {subconf} ]. self optionAt: 'path' ifPresent: [ :path | configuration outputFile: (RelativePath from: path) ]. self parseInputFile. self export. self exitSuccess if you are on chat somewhere let me know. Stef