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

Use new GET /subscription_user endpoint to populate subscription state #922

Open
4 tasks
eleanorreem opened this issue May 23, 2024 · 0 comments
Open
4 tasks
Labels
complexity: advanced Time needed to do this ticket will be large e.g. 2-3+ days maintenance Maintenance / chore work state: blocked Task is blocked.
Milestone

Comments

@eleanorreem
Copy link
Contributor

Overview

We want to start breaking up the GET /user/me request and only fetch information on the pages it is needed. This is starting with subscriptions. We are getting subscription information on every page when we actually only need it on the /subscription/whatsapp page. Please note this is potentially a large refactor.

Note this ticket is blocked by this issue on the backend.

Action Items

  • Take a look at the app/userSlice.ts
  • Stop populating subscription data on the userSlice from the /user/me request. Instead, populate subscriptions state only on the /subscription/whatsapp page using the new endpoint GET /subscription_user.
  • Ensure you can successfully subscribe and unsubscribe
  • Ensure Cypress tests pass
@eleanorreem eleanorreem added complexity: advanced Time needed to do this ticket will be large e.g. 2-3+ days maintenance Maintenance / chore work state: blocked Task is blocked. labels May 23, 2024
@kyleecodes kyleecodes added this to the 02. Roadmaps milestone May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity: advanced Time needed to do this ticket will be large e.g. 2-3+ days maintenance Maintenance / chore work state: blocked Task is blocked.
Projects
Status: To-Do Bloom Frontend
Development

No branches or pull requests

2 participants