merge branch: main

.env

@@ -1,2 +1,3 @@
 apiBaseUrl=https://sandbox.hyperswitch.io
-sdkBaseUrl=https://beta.hyperswitch.io/v1/HyperLoader.js
+sdkBaseUrl=https://beta.hyperswitch.io/v1/HyperLoader.js
+mixpanelToken=

.eslintrc.json

@@ -0,0 +1,17 @@
+{
+  "env": {
+    "browser": true,
+    "es2021": true,
+    "node": true,
+    "shelljs": true
+  },
+  "extends": [],
+  "parserOptions": {
+    "ecmaVersion": "latest",
+    "sourceType": "module"
+  },
+  "plugins": ["react-hooks"],
+  "rules": {
+    "react-hooks/rules-of-hooks": "error"
+  }
+}

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,87 @@
+name: Bug report
+description: Submit a bug report to help us improve
+title: "[BUG] "
+labels: ["C-bug", "S-awaiting-triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        We value your time and effort in submitting this bug report. Here are a few things to check before clicking the submit button :)
+        1. Make sure you're on the latest version of the app. The current release can be found here: https://github.com/juspay/hyperswitch-control-center/releases.
+        2. Search through **both** open and closed issues for your bug: https://github.com/juspay/hyperswitch-control-center/issues?q=is%3Aissue+sort%3Aupdated-desc+.
+        3. Please try to fill this template completely to the best of your abilities. A bug report that is clear and has a reproducible example lets us get to work faster.
+
+  - type: textarea
+    id: bug-description
+    attributes:
+      label: Bug Description
+      description: A clear and concise description of what the bug is.
+      placeholder: It bugs out when ...
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected-behavior
+    attributes:
+      label: Expected Behavior
+      description: What did you think should happen? Add request-response bodies, if applicable.
+      placeholder: It should ...
+    validations:
+      required: true
+
+  - type: textarea
+    id: actual-behavior
+    attributes:
+      label: Actual Behavior
+      description: What did actually happen? Add request-response bodies or screenshots, if applicable.
+      placeholder: It actually ...
+    validations:
+      required: true
+
+  - type: textarea
+    id: steps-to-reproduce
+    attributes:
+      label: Steps To Reproduce
+      description: How do you trigger this bug? Please walk us through it step by step.
+      value: |
+        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 '....'
+    validations:
+      required: true
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Context For The Bug
+      description: How has this issue affected you? What are you trying to accomplish?
+      placeholder: Providing context (e.g. request-response bodies, stack trace or log data) helps us come up with a solution that is most useful in the real world.
+    validations:
+      required: false
+
+  - type: checkboxes
+    id: no-duplicate-issues
+    attributes:
+      label: Have you spent some time checking if this bug has been raised before?
+      options:
+        - label: I checked and didn't find a similar issue
+          required: true
+
+  - type: checkboxes
+    id: read-contributing-guidelines
+    attributes:
+      label: Have you read the Contributing Guidelines?
+      options:
+        - label: I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch-control-center/blob/main/docs/CONTRIBUTING.md)
+          required: true
+
+  - type: dropdown
+    id: willing-to-submit-pr
+    attributes:
+      label: Are you willing to submit a PR?
+      description: This is absolutely not required, but we are happy to guide you in the contribution process.
+      options:
+        - Yes, I am willing to submit a PR!
+        - No, but I'm happy to collaborate on a PR with someone else
+        - No, I don't have time to work on this right now

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,11 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Discord server
+    url: https://discord.gg/wJZ7DVW8mm
+    about: Please ask any questions you may have here.
+  - name: Slack workspace
+    url: https://join.slack.com/t/hyperswitch-io/shared_invite/zt-1k6cz4lee-SAJzhz6bjmpp4jZCDOtOIg
+    about: Please ask any questions you may have here.
+  - name: GitHub Discussions
+    url: https://github.com/juspay/hyperswitch/discussions
+    about: Please ask and answer questions here.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,56 @@
+name: Feature request
+description: Submit a proposal for a new feature
+title: "[FEATURE] "
+labels: ["C-feature", "S-awaiting-triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        We value your time and efforts in submitting this feature request form. Here are a few things to check before clicking the submit button :)
+        1. Make sure you're on the latest version of the app. Features are being added all the time, and it is entirely possible what you're requesting has already been added. The current release can be found here: https://github.com/juspay/hyperswitch-control-center/releases.
+        2. Check the changelog file to confirm that the feature hasn't been added for an upcoming release: https://github.com/juspay/hyperswitch-control-center/blob/main/CHANGELOG.md
+        3. Please try to fill this template completely to the best of your abilities. A feature request that is clear and explicit in its needs lets us get to work faster.
+
+  - type: textarea
+    id: feature-description
+    attributes:
+      label: Feature Description
+      description: A clear and concise description of what the feature is.
+      placeholder: In my use-case, ...
+    validations:
+      required: true
+
+  - type: textarea
+    id: implementation
+    attributes:
+      label: Possible Implementation
+      description: A clear and concise description of what you want to happen.
+      placeholder: Not obligatory, but ideas as to the implementation of the addition or change
+    validations:
+      required: true
+
+  - type: checkboxes
+    id: no-duplicate-issues
+    attributes:
+      label: Have you spent some time checking if this feature request has been raised before?
+      options:
+        - label: I checked and didn't find a similar issue
+          required: true
+
+  - type: checkboxes
+    id: read-contributing-guidelines
+    attributes:
+      label: Have you read the Contributing Guidelines?
+      options:
+        - label: I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch-control-center/blob/main/docs/CONTRIBUTING.md)
+          required: true
+
+  - type: dropdown
+    id: willing-to-submit-pr
+    attributes:
+      label: Are you willing to submit a PR?
+      description: This is absolutely not required, but we are happy to guide you in the contribution process.
+      options:
+        - Yes, I am willing to submit a PR!
+        - No, but I'm happy to collaborate on a PR with someone else
+        - No, I don't have time to work on this right now

.github/workflows/eslint-check.yml

@@ -0,0 +1,30 @@
+name: ESLint
+
+on: [push]
+
+jobs:
+  eslint:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v2
+        with:
+          fetch-depth: 0
+          token: ${{ secrets.AUTO_RELEASE_PAT }}
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v3
+        with:
+          node-version: 18
+
+      - name: Install dependencies
+        run: npm install --force
+
+      - name: Build Rescript
+        run: npm run re:build
+
+      - name: Run ESLint
+        run: npm run lint:hooks
+        env:
+          CI: true

.gitignore

@@ -20,3 +20,4 @@ yarn.lock
 user_data.sh
 *.pem
 .bsb.lock
+package-lock.json