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.

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

[BUG]: 2-Letter State abbreviation is not accepted #4647

Closed
2 tasks done
SamraatBansal opened this issue May 15, 2024 · 0 comments · Fixed by #4646
Closed
2 tasks done

[BUG]: 2-Letter State abbreviation is not accepted #4647

SamraatBansal opened this issue May 15, 2024 · 0 comments · Fixed by #4646
Assignees
Labels
C-bug Category: Bug

Comments

@SamraatBansal
Copy link
Contributor

Bug Description

Currently 2-Letter State abbreviation is not accepted, in billing.state if you pass 2 letter valid state it should not throw an error

Expected Behavior

Both 2 letter and full state name shall be accepted in billing.state and should be manipulated according to the requirements before sending it to the connector.

Actual Behavior

Currently 2-Letter State abbreviation is not accepted, in billing.state if you pass 2 letter valid state it should not throw an error

Steps To Reproduce

Provide an unambiguous set of steps to reproduce this bug. Include code or configuration to reproduce, if relevant.

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'

Context For The Bug

No response

Environment

Are you using hyperswitch hosted version? Yes/No
If yes, please provide the value of the x-request-id response header to help us debug your issue.

If not (or if building/running locally), please provide the following details:

  1. Operating System or Linux distribution:
  2. Rust version (output of rustc --version): ``
  3. App version (output of cargo r --features vergen -- --version): ``

Have you spent some time checking if this bug has been raised before?

  • I checked and didn't find a similar issue

Have you read the Contributing Guidelines?

Are you willing to submit a PR?

Yes, I am willing to submit a PR!

@SamraatBansal SamraatBansal added C-bug Category: Bug S-awaiting-triage Status: New issues that have not been assessed yet labels May 15, 2024
@SamraatBansal SamraatBansal self-assigned this May 15, 2024
@SamraatBansal SamraatBansal linked a pull request May 15, 2024 that will close this issue
14 tasks
@SanchithHegde SanchithHegde removed the S-awaiting-triage Status: New issues that have not been assessed yet label May 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: Bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants