-
Notifications
You must be signed in to change notification settings - Fork 3
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
v5.0.0 #119
Merged
Merged
v5.0.0 #119
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…e pair. Resolves #117
…ey-value-pair-n/117 Restrict `target_keys` object to contain only a single key value pair.
/diff |
Here are your diffs for this pull request
|
elray1
approved these changes
Jan 17, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
zkamvar
approved these changes
Jan 17, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thank you also for updating the round_name
example
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In this PR I've mainly just bumped the version to v5.0.0 instead on v4.0.1 to signify a breaking change in the schema
The major changes have been reviewed in #116 and #118 already but I've moved them to this PR instead.
I've also gone ahead and removed
target_variable
andtarget_outcome
from the standard task IDs in the schema.Going to move on to updating
hubAdmin
now.Explicit validation of
round_id
formatThis PR Resolves #112 by adding a regex pattern check to the
round.round_id
property whenround.round_id_from_variable
id false. This provides upfront validation of the expected format of manual round IDs (i.e. not from a variable). It contains no breaking changes (Hub's can change to the version without making any further changes to their configs)When
round.round_id_from_variable
is true, validation will be handled dynamically in hubAdmin (hubverse-org/hubAdmin#68)Validation of the checks can be found in the
hubAdmin
PR added tests: https://github.com/hubverse-org/hubAdmin/blob/30923f58bac47484fd80860ba491a334876a279e/tests/testthat/test-create_round.R#L371-L474 and associated test files and snaphotsRestrict
target_keys
to single key pair valueThis PR also resolves #117 by restricting
target_keys
objects to contain only a single key value pair.Successful validation is demonstrated in
hubAdmin
PR hubverse-org/hubAdmin#90 and more specifically in these tests using this and this test file.