Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[FIX] fix response for migration api #6526

Closed
prasunna09 opened this issue Nov 11, 2024 · 0 comments · Fixed by #6525
Closed

[FIX] fix response for migration api #6526

prasunna09 opened this issue Nov 11, 2024 · 0 comments · Fixed by #6525
Assignees
@prasunna09
Labels
C-bug Category: Bug
Milestone
December 2024 Rel...

Comments

@prasunna09
Copy link
Contributor

Currently there is inconsistent response due to no validations for request body fields for the migration api.

Implementation -
validations such as empty string check for network transaction id and empty object for connector mandate details should be enforced while evaluating the migration response.
@prasunna09 prasunna09 added the C-bug Category: Bug label Nov 11, 2024
@prasunna09 prasunna09 added this to the November 2024 Release milestone Nov 11, 2024
@prasunna09 prasunna09 self-assigned this Nov 11, 2024
@prasunna09 prasunna09 linked a pull request Nov 11, 2024 that will close this issue
fix(router): validate each field for migration request body #6525
Merged
14 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@prasunna09 prasunna09

Labels
C-bug Category: Bug
Projects
None yet
Milestone
December 2024 Release
Development

Successfully merging a pull request may close this issue.

fix(router): validate each field for migration request body juspay/hyperswitch
2 participants
@SanchithHegde @prasunna09