dest: return proper data in graphql errors #3676
Merged
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
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.
Which issue(s) this PR fixes:
This PR adds a normalized output to destination validation errors (currently only called from contact method input
destfield).extensions.codewill be one of:INVALID_DESTINATION_TYPEorINVALID_DESTINATION_FIELD_VALUE.pathproperty of errors will reflect the actual input field (and fieldID) that failed validationOut of Scope:
Since no code currently uses this, tests will be added with the user contact method dialog PR(s).
Describe any introduced user-facing changes:
N/A
Describe any introduced API changes:
Additional Info:
Existing field errors are unaffected.