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

515-flag-column-values-are-inconsistent-rejected-invalid-suspect-vs-accepted-valid-pass-1 #532

Merged
merged 12 commits into from
Nov 8, 2024

Conversation

wokenny13
Copy link
Collaborator

Using 'Suspect' and 'Pass' for consistency.

Using 'Suspect' and 'Pass' for consistency.
@wokenny13
Copy link
Collaborator Author

@hillarymarler @cristinamullin

This should be ready for review now.

Ensuring that all the flagging function outputs are accurate and any documentation/comment changes (changing any instances of 'invalid' or 'rejected' to 'suspect' and any instances of 'valid' or 'accepted' to 'pass') where appropriate should be done as part of the review process.

@cristinamullin
Copy link
Collaborator

@wokenny13 can you write up a brief overview for TADA users - which functions are impacted and which specific values within the columns created by those functions? This will help them update their workflows to be compatible (a crosswalk from old to new names may be helpful). I'll share it with our contact list after this PR is merged in. Thank you in advance!

@cristinamullin cristinamullin merged commit 4d6beec into develop Nov 8, 2024
1 of 7 checks passed
@cristinamullin cristinamullin deleted the flagging branch November 8, 2024 19:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Flag column values are inconsistent (Rejected, Invalid, Suspect vs. Accepted, Valid, Pass)
3 participants