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] When adding a new customer and setting up a Stripe connection, the site should poll for new potential Stripe connections whenever the user interacts with the dropdown #1476

Closed
doctorpangloss opened this issue Apr 25, 2024 · 2 comments · Fixed by #1463

Comments

@doctorpangloss
Copy link

Describe the bug
Adding a stripe connection in another page should make it appear in the dropdown.

In general, the forms should do a better job retaining information as you interact with the site.

To Reproduce

  1. Visit the /customers route
  2. Add a customer
  3. Navigate down to Payment provider information.
  4. Click default payment provider: stripe
  5. Observe no connected accounts.
  6. Open a new tab, configure a Stripe account.
  7. Observe that the connected accounts dropdown is not updated. It should be.

Expected behavior
Update the dropdown as soon as a connected account is added or the user interacts with the dropdown.

Environment infos

Environment informations

App environment : production
API URL : xxx
Version : 1.0.0 (really 1.2.1)
User Id : 52e9cbc7-69dd-4f26-b44c-38df742498d5

@doctorpangloss doctorpangloss added the 🐞 bug Something isn't working label Apr 25, 2024
@ansmonjol
Copy link
Collaborator

This part of the app will very soon be refactored.

I'll have this case in mind during implementation.

Thanks for reporting

@ansmonjol ansmonjol added 🌈 improvement and removed 🐞 bug Something isn't working labels May 6, 2024
@ansmonjol
Copy link
Collaborator

This will be fixed by #1463

Payment integration will be fetched each time you open the accordion - the one dedicated to selecting the Stripe (or other PP) linked account.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants