To reduce notifications, issues are locked until they are 🏁 status: ready for dev You can asked for this issue to be assigned (if not already assigned) and to be assigned. You can learn more in our contributing guide https://github.com/EddieHubCommunity/BioDrop/blob/main/CONTRIBUTING.md

Confirmed this bug is happening and I will unlock, however, I am not able to assign this issue to you as you have not explained your approach to solve this. Can you please add more detail on what you would like to do to address the issue?

The issue has been unlocked and is now ready for dev. If you would like to work on this issue, you can comment to have it assigned to you. You can learn more in our contributing guide https://github.com/EddieHubCommunity/BioDrop/blob/main/CONTRIBUTING.md

I would like to work on this issue , can you assign this to me . I know I have another issue, but I solved it and sent a pull request , waiting for getting merge.

ℹ️ pratik9818 has some opened assigned issues: 🔧View assigned issues

Interested

@pratik9818 your PR for your existing issue will need to be merged before we assign another issue to you. This ensures a fair approach and gives everyone an opportunity to contribute.

In any event, as Amanda mentioned (@jatingodnani please also take note of this) - this issue cannot be assigned until whoever is looking to work on it explains their approach to resolving it.

@SaraJaoude, I found the bug in the code. We are rendering two things: 'users' and 'visibleUsers.' 'Users' contains an array of updated users, while 'visibleUsers' contains an array of search results due to a query from the 'users' array. 'VisibleUsers' takes some time to render, so I added a loading indicator. We don't need to render updated users every time; we only show updated users if the input box is empty.

@SaraJaoude, I found the bug in the code. We are rendering two things: 'users' and 'visibleUsers.' 'Users' contains an array of updated users, while 'visibleUsers' contains an array of search results due to a query from the 'users' array. 'VisibleUsers' takes some time to render, so I added a loading indicator. We don't need to render updated users every time; we only show updated users if the input box is empty.

Thank you for explaining the approach you would like to take. I will assign this to you to begin work on the proposed solution.

Unassigning for this reason: #9788 (comment)

I see this is no longer assigned. Noticed it does not have the [good first issue] label, but still has 3 or less points. I managed to setup the env locally and I would like to work on it by doing the following:

• create a reusable Loading component under components folder
• keep the loading flag as a state and set it to true/false inside the fetchUsers method (true when starts, false when ends with success/error)
• when the loading is true render the reusable Loading component, otherwise render the actual users list

Extra:

• maybe add some loading delay support just not to have the loading spinner flickering if the loading time is very short
• get rid of the extra logic of rendering the list with {users.length < usersPerPage && and {users.length > usersPerPage && since const visibleUsers = users.slice(indexOfFirstUser, indexOfLastUser); will always return the visible users in range even if the indexOfLastUser is bigger than the actual users array

@stefanzmf Assigning the issue to you

Opened the PR. Please let me know if there are further steps that needs to be done from my side. Thank you

ℹ️ stefanzmf has some opened assigned issues: 🔧View assigned issues