-
Notifications
You must be signed in to change notification settings - Fork 18
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
Conversation
Using 'Suspect' and 'Pass' for consistency.
other changes to documentations for 'invalid' text to 'suspect' text.
@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. |
@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! |
Using 'Suspect' and 'Pass' for consistency.