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

refactor: proper identification of reactHyperJs from hyperswitch #299

Merged
merged 6 commits into from
Jan 30, 2024

Conversation

jainlokesh318
Copy link
Contributor

Type of Change

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

Description

Motivation and Context

How did you test it?

Checklist

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

@jainlokesh318 jainlokesh318 added the S-waiting-on-review Status: This PR has been implemented and needs to be reviewed label Jan 24, 2024
@jainlokesh318 jainlokesh318 self-assigned this Jan 24, 2024
@jainlokesh318 jainlokesh318 requested a review from a team as a code owner January 24, 2024 10:12
@jainlokesh318 jainlokesh318 changed the title fix: proper identification of reactHyperJs from hyperswitch refactor: proper identification of reactHyperJs from hyperswitch Jan 24, 2024
@PritishBudhiraja PritishBudhiraja added this pull request to the merge queue Jan 30, 2024
Merged via the queue into main with commit 4038dff Jan 30, 2024
5 checks passed
@github-actions github-actions bot added Closed Applied to issues or pull requests that have been successfully resolved or completed and removed S-waiting-on-review Status: This PR has been implemented and needs to be reviewed labels Jan 30, 2024
@PritishBudhiraja PritishBudhiraja deleted the fix/reactHyperJs branch March 28, 2024 05:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Closed Applied to issues or pull requests that have been successfully resolved or completed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants