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

Remove therapySession join from userService.getUserProfile table #717

Open
2 tasks
kyleecodes opened this issue Dec 7, 2024 · 5 comments
Open
2 tasks
Assignees
Labels
complexity: beginner Time needed to do this ticket is less than 1 day. help-wanted Extra attention is needed refactor SQL testing-required
Milestone

Comments

@kyleecodes
Copy link
Member

Overview

The therapySession join in the userService.getUserProfile table is unnecessary as the frontend does not use this data.

Action Items

  • Remove the therapySession join from userService.getUserProfile table.
  • Clean up tests associated with this change, running Cypress tests from the frontend to confirm no functionality is broken.

Resources

@kyleecodes kyleecodes added complexity: beginner Time needed to do this ticket is less than 1 day. help-wanted Extra attention is needed refactor SQL testing-required labels Dec 7, 2024
@kyleecodes kyleecodes added this to the 02. Roadmaps milestone Dec 7, 2024
@csehatt741
Copy link

@kyleecodes, may I work on this issue?

Copy link

Thank you @csehatt741 you have been assigned this issue!
Please follow the directions in our Contributing Guide. We look forward to reviewing your pull request. ✨


Support Chayn's mission? ⭐ Please star this repo to help us find more contributors like you!
Learn more about our impact and sign-up for our volunteer programsto join our mission!. 🌸

@csehatt741
Copy link

@kyleecodes, I need some help to set-up local users:

After creating a super admin I cannot create the partner admin, as in /admin/dashboard page at Create an admin account the Select the partner drop-down is empty, but this field is a required one.

Database has been restored, as described and there are three partners in the partner table.

What do I miss here?

@kyleecodes
Copy link
Member Author

@csehatt741 thanks for reaching out!

This is caused with by the backend not interacting with the frontend properly, as the backend contains the partner options. This is usually due to improper database population.
Can you confirm that the database was populated by using a SQL query? Without creating users you can confirm via this query:
SELECT * FROM public."user" users WHERE users."email" = 'tech+cypresspublic@chayn.co';

@csehatt741
Copy link

I can confirm this query returns the tech+cypresspublic@chayn.co user record.

I've already created 3 users (public user, super admin and a partner user respectively) by following the instructions in the Local Bloom User Set-Up Guide.

Unfortunately, I`m facing issues with creating the partner admin ones.

I`ll debug the code and will take a look what goes wrong!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity: beginner Time needed to do this ticket is less than 1 day. help-wanted Extra attention is needed refactor SQL testing-required
Projects
None yet
Development

No branches or pull requests

2 participants