Very early draft, some issues still remain, experimental and ee may not wanto to go this route, but wanted to push it to have something to show the team.
The most useful use-case for this would be something similar to this CCI recipe PR, in which old versions deprecate option values in favour of new ones (As their value is directly passed to the build system)
The current solution goes the validate() route, which although it lets the recipe present nicer errors to the users, it could quickly grow unmanageable after a few changes like that.
There might be an alternative approach: The init method might run early enough to be able to redefine the self.options dict-like value before it gets converted to a _PackageOptions object
Changelog: TODO Docs: TODO
Very early draft, some issues still remain, experimental and ee may not wanto to go this route, but wanted to push it to have something to show the team.
The most useful use-case for this would be something similar to this CCI recipe PR, in which old versions deprecate option values in favour of new ones (As their value is directly passed to the build system)
The current solution goes the
validate()route, which although it lets the recipe present nicer errors to the users, it could quickly grow unmanageable after a few changes like that.There might be an alternative approach: The
initmethod might run early enough to be able to redefine theself.optionsdict-like value before it gets converted to a_PackageOptionsobject