Feature/admin dashboard event visualization 407

[cblanken]

Description

Display all current events on Admin Dashboard. The AdminDashboard page now loads all current events and displays them in a list. The page initially loads all the current events automatically, but any subsequent refreshes must use the "Refresh Events" button in the top right.

NOTE: All tests passed for the first two commits cdd0cd7 and cbfaa9f. However, the Admin dashboard cannot currently be accessed while running the development build due to an old /calendar redirect in client/src/contexts/AuthContext/useProvideAuth.js. The latest commit d6db77b removes this redirect for testing the Admin Dashboard, but some adjustments will need to be made to the relevant failing tests.

I've attached test-events.zip with a json file that can be imported into the events Mongo collection to test the loading animation with a large set of events.

Page while loading

Page after load

Type of change

Please select everything applicable. Please, do not delete any lines.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• This change requires an update to testing

Issue

• Is this related to a specific issue? If so, please specify: Visualize all events returned from getAll #407

Checklist:

• This PR is up to date with the main branch, and merge conflicts have been resolved
• I have executed npm run test and all tests have passed successfully or I have included details within my PR on the failure.
• I have executed npm run lint and resolved any outstanding errors. Most issues can be solved by executing npm run format
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings

[Caleb-Cohen]

Code looks good. Should we consider additional testing?

For example: insert event into DB, does it visualize?

[Caleb-Cohen]

Looks good so far, what are your thoughts on deleting the event and checking if it no longer exists?

[cblanken]

Looks good so far, what are your thoughts on deleting the event and checking if it no longer exists?

My thinking is that I should be able to send a DELETE to the /event/:id endpoint and just delete any notes by id. I might add a Cypress command like deleteOwnEvents to make it a bit easier to use.

Then the rendering check can loop through any remaining notes and confirm the note with the target id no longer exists.

I should be able to take a look at it in the next couple days and let you know if I run into any issues with that method.

[Caleb-Cohen]

Looks good so far, what are your thoughts on deleting the event and checking if it no longer exists?

My thinking is that I should be able to send a DELETE to the /event/:id endpoint and just delete any notes by id. I might add a Cypress command like deleteOwnEvents to make it a bit easier to use.

Then the rendering check can loop through any remaining notes and confirm the note with the target id no longer exists.

I should be able to take a look at it in the next couple days and let you know if I run into any issues with that method.

That's how I would approach it!

[Caleb-Cohen]

LGTM Thanks for taking this on!