[Cherrypick][PLUGIN-1952] and version update for unsupported field name message#149
Open
Ashutosh-Jarvis wants to merge 2 commits intodata-integrations:release/1.2from
Conversation
98153ff to
d18ebee
Compare
This file contains hidden or 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.
cherry picked: d0ae86f
PR Link: #147
fix: include specific field name in error message
What:
Updated the validation logic / error handler to append the exact field name to the resulting output message.
Why:
Previously, the message was too generic, making it difficult to identify exactly which data column triggered the issue. Including the specific field name provides immediate context.
Testing:
Tested by creating the jar of this plugin in local and embedding it with Servicenow connector.
updated version from 1.2.10 to 1.2.11-SNAPSHOT