Hook in APIs to filtered permissions data component

[JackHaeg]

Dependency

• This issue is cleared to be assigned/worked on until Create filtered permissions data component #1754 has been completed, and API issues (Create API call to get all users who are listed as VRMS Admins #1770 & Create API call to get all users who are listed as managers on a project #1771) PRs have been approved.
• This issue should be worked on and resolved from the feature branch user_permissions_search. Please pull down that branch to work on this issue.

git fetch vrms # or "git fetch upstream" depending on your remotes configuration
git branch user_permissions_search
git checkout -b [new branch name]

Overview

This issue represents the final step in the User Permission Search Epic. The objective is to remove the placeholder dummy data currently used in the "User Permission Search" screen and integrate the APIs developed earlier in the Epic. Once completed, the filtered permissions data component will be fully functional and ready for production.

Action Items

• Remove Dummy Data
  • Identify and remove all instances of dummy/placeholder data from the "User Permission Search" screen and filtered permissions data component.
• API Integration
  • Hook up the previously created APIs to the filtered permissions data component within the following feature branch: https://github.com/hackforla/VRMS/tree/user_permissions_search:
    • For Admin: Added an API that fetches all the admins #1774
    • For Project Leads: 1771 - API for Fetching Project Managers  #1799
  • Ensure the API responses are correctly mapped to the UI elements and behave as expected.
• Testing
  • Verify the full flow from user input to permission search results.
  • Ensure that the search results update dynamically based on input filters.
  • Conduct both unit tests and end-to-end tests to validate the functionality and catch any edge cases.

Resources/Instructions

Screenshot of User Permission Search Screen mockups

• Low-fi mockups created by Bonnie / Jack - see page 2 of mockups
• This issue is part of this epic: Epic - User Permission Search #1737

[JackHaeg]

@trillium Please add an action item to address any remaining dummy data objects, values, or properties not currently included in our code, as noted by Vorleak in this PR #1808 (comment)

[JackHaeg]

@vorleakyek this issue is cleared to be worked on now that the PRs have been merged. Given that you expressed interested in working on this issue previously (and you have worked on previous issues in this Epic), I went ahead and assigned you to the issue / placed the issue in progress. Please let me know if you are okay with this by liking this comment. Also, please reach out to @trillium if you have any questions!

[vorleakyek]

Hi @JackHaeg!

Progress: I started to take a look at how the API was implemented in 1771 - API for Fetching Project Managers #1799.
Blockers: There were comments under that PR, so I'm trying to understand and resolve it.
Availability: I'm available 3-6 hrs this week.
ETA: possible in 1 or 2 weeks

[JackHaeg]

Thanks for the update @vorleakyek! Please reach out to @trillium with any questions related to the comments on the PR you mentioned in your comment above.

[JackHaeg]

Hi @vorleakyek! When you have a moment, can you please provide an update with the following information:

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures or links* (if necessary): "Add any pictures or links that will help illustrate what you are working on."

• remember to add links to the top of the issue if they are going to be needed again.

[vorleakyek]

Hi @JackHaeg!

Progress: I had to adjust the data structure fetched from the project lead API (#1799) to match the frontend dummy data. I'm almost done with it. So, I'll have PR up probably by Wednesday.
Blockers: I might have to dig into unit tests since I'm not familiar with it.
Availability: I'm available 3-6 hrs this week.
ETA: I should have a PR up by Wednesday.

[JackHaeg]

Thanks for the update, @vorleakyek! Looking forward to checking out the PR soon :)