[R20-1666] add non-pii form data to submission events #972
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
✅ Deploy Preview for ripple-docs canceled.
|
dylankelly
approved these changes
Jan 1, 2024
…ld events include value
Passing run #1094 ↗︎
Details:
Review all test suite changes for PR #972 ↗︎ |
|||||||||||||||
waitingallday
approved these changes
Jan 8, 2024
# Conflicts: # packages/ripple-ui-forms/src/inputs/dropdown.ts
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.
Issue: https://digital-vic.atlassian.net/browse/R20-1666
What I did
Right now all editable fields are treated as potentially containing pii. So things like radio buttons, checkboxes and selects are marked as non-pii in the webform mapping. If the backend adds support for pii we can set the pii state on a field by field basis.
How to test
Checklist
For all PR's
For new components only