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

fix: added support for Customization for PaymentMethodHeaderText #283

Merged
merged 2 commits into from
Apr 10, 2024

Conversation

ArushKapoorJuspay
Copy link
Contributor

Type of Change

  • Bugfix
  • New feature
  • Enhancement
  • Refactoring
  • Dependency updates
  • Documentation
  • CI/CD

Description

Added support for Customization for PaymentMethodHeaderText under appearance with className .PaymentMethodsHeaderLabel

Checklist

  • I ran npm run re:build
  • I reviewed submitted code
  • I added unit tests for my changes where possible

@PritishBudhiraja PritishBudhiraja added the Ready for Review PR with label Ready for Review should only be reviewed. label Apr 10, 2024
@prafulkoppalkar prafulkoppalkar merged commit bdbd84a into main Apr 10, 2024
3 checks passed
@prafulkoppalkar prafulkoppalkar deleted the fix/payment-method-header-label-customization branch April 10, 2024 10:32
akash-c-k pushed a commit that referenced this pull request Apr 10, 2024
## [0.39.1](v0.39.0...v0.39.1) (2024-04-10)

### Bug Fixes

* added support for Customization for PaymentMethodHeaderText ([#283](#283)) ([bdbd84a](bdbd84a))
rising-dragon401 added a commit to rising-dragon401/hyperswitch-web that referenced this pull request Jul 2, 2024
## [0.39.1](juspay/hyperswitch-web@v0.39.0...v0.39.1) (2024-04-10)

### Bug Fixes

* added support for Customization for PaymentMethodHeaderText ([#283](juspay/hyperswitch-web#283)) ([bdbd84a](juspay/hyperswitch-web@bdbd84a))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Ready for Review PR with label Ready for Review should only be reviewed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants