-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
refactor(router): add the connector_label
field to DuplicateMerchantConnectorAccount
error message
#1044
refactor(router): add the connector_label
field to DuplicateMerchantConnectorAccount
error message
#1044
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
connector_label
field to DuplicateMerchantConnectorAccount
error message
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks Good. Thanks for the contribution @EliKalter. You can also add this field to MerchantConnectorNotFound
error message.
MerchantConnectorAccountNotFound, |
If interested, please create an issue and take it up in a separate PR.
Cheers.
I'll do it. |
Type of Change
Description
This PR adds the connector_label to the message of the DuplicateMerchantConnectorAccount variant in the ApiErrorResponse enum
Additional Changes
Motivation and Context
This resolves #899,
The connector_label is created by Hyperswitch internally hence it is necessary to send back the connector_label is the error response so that the user has an idea of what the connector_label is.
How did you test it?
Checklist
cargo +nightly fmt --all
cargo clippy