This task was to update the event model to include a new status field with a default value of pending. The required parameter was set to true as well.
This PR does not need to be merged yet. Until there is more discussion around updating the production database. There is the option of using a Python script to connect to the database and update all documents in the event collection that do not have a status field currenlt
Type of change
Please select everything applicable. Please, do not delete any lines.
[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[X] This change requires a documentation update
[ ] This change requires an update to testing
Issue
[X] Is this related to a specific issue? If so, please specify: #408
Checklist:
[X] 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. - We should probably find a replacement for cross-env it has been under maintenance for 2 years with very little updates.
[X] I have executed npm run lint and resolved any outstanding errors. Most issues can be solved by executing npm run format
[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
Description
This task was to update the event model to include a new
status
field with a default value ofpending
. Therequired
parameter was set totrue
as well.This PR does not need to be merged yet. Until there is more discussion around updating the production database. There is the option of using a Python script to connect to the database and update all documents in the event collection that do not have a status field currenlt
Type of change
Please select everything applicable. Please, do not delete any lines.
Issue
Checklist:
npm run test
and all tests have passed successfully or I have included details within my PR on the failure. -We should probably find a replacement for cross-env it has been under maintenance for 2 years with very little updates.
npm run lint
and resolved any outstanding errors. Most issues can be solved by executingnpm run format