Argument derived_task_ids has been introduced to hubValidations 0.5.0 allowing such task IDs to be largely ignored in favour of simpler checks on their values. However, the only way to deploy this currently is manually though the derived_task_ids argument in the relevant validate_*() functions.
It would be good to be able to record derived task IDs somewhere in the config and for relevant validate_*() functions to be able to make use of them.
Derived task IDs can cause a number of issues to validation (see eg https://github.com/orgs/hubverse-org/discussions/26, https://github.com/hubverse-org/hubValidations/issues/38), most importantly they can create unneccessary strain on memory during validation by polluting expanded grids of valid values with invalid value combinations.
Argument
derived_task_idshas been introduced tohubValidations 0.5.0allowing such task IDs to be largely ignored in favour of simpler checks on their values. However, the only way to deploy this currently is manually though thederived_task_idsargument in the relevantvalidate_*()functions.It would be good to be able to record derived task IDs somewhere in the config and for relevant
validate_*()functions to be able to make use of them.