Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create property to record derived task IDs #96

Closed
annakrystalli opened this issue Aug 15, 2024 · 0 comments · Fixed by #103
Closed

Create property to record derived task IDs #96

annakrystalli opened this issue Aug 15, 2024 · 0 comments · Fixed by #103
Assignees
Labels
higher priority work to prioritize in the near future

Comments

@annakrystalli
Copy link
Member

Derived task IDs can cause a number of issues to validation (see eg https://github.com/orgs/hubverse-org/discussions/26, hubverse-org/hubValidations#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_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.

@annakrystalli annakrystalli added this to the optimise-validations milestone Aug 15, 2024
@annakrystalli annakrystalli moved this from Todo to Up Next in hubverse Development overview Aug 15, 2024
@bsweger bsweger added the higher priority work to prioritize in the near future label Sep 25, 2024
@annakrystalli annakrystalli self-assigned this Sep 27, 2024
@annakrystalli annakrystalli moved this from Up Next to In Progress in hubverse Development overview Oct 9, 2024
@annakrystalli annakrystalli mentioned this issue Oct 9, 2024
@annakrystalli annakrystalli linked a pull request Oct 9, 2024 that will close this issue
@annakrystalli annakrystalli moved this from Ready for Review to Reviewed/Ready to Merge in hubverse Development overview Oct 16, 2024
@github-project-automation github-project-automation bot moved this from Reviewed/Ready to Merge to Done in hubverse Development overview Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
higher priority work to prioritize in the near future
Projects
Development

Successfully merging a pull request may close this issue.

2 participants