feat: sdk config api integration

[Shivam25092001]

Type of Change

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

Description

• Extract profile_id from client_secret. Changes as per feat: extract profile id from client secret #1550
• sdk-configs api integration
• Corresponding api contract details in PR description at: feat(core): Added eligible connector and payment_method as a part of sdk configs api hyperswitch#12667
• Closes Integrate 'sdk-configs' api for superposition-raw-configs #1580
• added support of sdk config in preloadSDKWithParams. new structure ->

let options = {
{
    clientSecret,
    appearance: {
      labels: "floating",
      // theme: "brutal",
    },
    preloadSDKWithParams: params,
  };
}

<HyperElements hyper={hyperPromise} options={options}>
          <CheckoutForm />
        </HyperElements>

{
    paymentMethodsList: ... ,
    customerMethodsList: ... ,
    sessionTokens: ...,
    sdkConfigs: ...
}

How did you test it? [TESTING TO BE DONE AFTER BACKEND DEPLOYMENT]

Added a console.log in DynamicFields.res file to print the sdkConfigs state.

  let sdkConfig = Recoil.useRecoilValueFromAtom(sdkConfigs)
  Console.log2("-- DynamicFields sdkConfigs -- ", sdkConfig)

• Tried passing sdkAuthorization in <HyperElements hyper={hyperPromise} options={{sdkAuthorization}}>, profile_id retrieved successfully and sdk-configs api fetched properly.
• Tried passing profile_id in window.Hyper({ publishableKey, profileId }), profile_id retrieved successfully and sdk-configs api fetched properly.
• Tried passing older cs without attached profiled_id, got integration error in console.
• Also tested by passing preloadSDKWithParams.

Checklist

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

[semanticdiff-com]

Review changes with  

[github-actions]

🚫 Missing Linked Issue

Hi 👋 This pull request does not appear to be linked to any open issue yet.

Linking your PR to an issue helps keep the project tidy and ensures the issue is closed automatically.

✔️ How to fix this

• Add a keyword like Fixes #123 or Closes #456 to your PR description or a commit message.
• Or link it manually using the "Linked issues" panel in the PR sidebar.

✅ Tip: You can link multiple issues.
🚫 Note: If only one issue is linked, it must be open for this check to pass.

Once linked, this check will pass automatically on your next push or when you re-run the workflow.

Thanks for helping maintainers! 🙌

[aritro2002]

please add more description and test cases images and video. Link issue.

[github-actions]

🚫 Missing Linked Issue

Hi 👋 This pull request does not appear to be linked to any open issue yet.

Linking your PR to an issue helps keep the project tidy and ensures the issue is closed automatically.

✔️ How to fix this

• Add a keyword like Fixes #123 or Closes #456 to your PR description or a commit message.
• Or link it manually using the "Linked issues" panel in the PR sidebar.

✅ Tip: You can link multiple issues.
🚫 Note: If only one issue is linked, it must be open for this check to pass.

Once linked, this check will pass automatically on your next push or when you re-run the workflow.

Thanks for helping maintainers! 🙌

[aritro2002]

also please check the PR title, and other S conventions which are not followed.

[github-actions]

🚫 Missing Linked Issue

Hi 👋 This pull request does not appear to be linked to any open issue yet.

Linking your PR to an issue helps keep the project tidy and ensures the issue is closed automatically.

✔️ How to fix this

• Add a keyword like Fixes #123 or Closes #456 to your PR description or a commit message.
• Or link it manually using the "Linked issues" panel in the PR sidebar.

✅ Tip: You can link multiple issues.
🚫 Note: If only one issue is linked, it must be open for this check to pass.

Once linked, this check will pass automatically on your next push or when you re-run the workflow.

Thanks for helping maintainers! 🙌

[github-actions]

🚫 Missing Linked Issue

Hi 👋 This pull request does not appear to be linked to any open issue yet.

Linking your PR to an issue helps keep the project tidy and ensures the issue is closed automatically.

✔️ How to fix this

• Add a keyword like Fixes #123 or Closes #456 to your PR description or a commit message.
• Or link it manually using the "Linked issues" panel in the PR sidebar.

✅ Tip: You can link multiple issues.
🚫 Note: If only one issue is linked, it must be open for this check to pass.

Once linked, this check will pass automatically on your next push or when you re-run the workflow.

Thanks for helping maintainers! 🙌