Bug Fix: fetch logic to display users #498
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #471
This PR updates the user fetch logic with the user's JW token. In our backend, we updated our get all users endpoint to require the admin role in the user's JW Token. This restriction prevented the edit user role page from fetching all users from database.
The commit includes the ability to disable strict mode in the next.config.js file. Using useEffect to trigger a fetch call in strict mode causes the fetch request to fire twice. After further investigation, I found that strict mode is enabled by default in next.js. I included it as a quick way to disable strict mode when testing API endpoints using the front-end.
How to test
Note: Double check the back-end listener is set to 3000 since front-end expects the backend port to be set at 3000.
Results: