Follow-up from "WIP: Redesign of job options management"
The following discussion from !577 (merged) should be addressed:
-
@clemenci started a discussion: This is needed because the old
JobOptionsSvc
was usingProperty<string>
as an exchange format between different property types, basically equivalent to:Property<bool> m_flag{false}; m_flag.assign( Property<string>{"true"} );
which lead to an asymmetry between
Property<string>
andProperty<T>
fortoString
andfromString
(see GAUDI-1232).Unfortunately the pattern is used in client code, so we cannot really drop support for it until we have a way to warn when user code relies on it, to then fix it.