TECH-394: Admin client notifications

npham49 commented 11 months ago

Description of changes:

Added Notification CRUD endpoint on Admin API for adding and removing notification entries.
Added Notification table with the following schema: ( id SERIAL NOT NULL, email character varying(255) COLLATE pg_catalog."default", username character varying(255) COLLATE pg_catalog."default", catchmentno integer, type character varying(255) COLLATE pg_catalog."default" ) which will contains all mappings between users/their emails and the catchment they are subscribed to.
Switched Form API to accept connection only from the Employer API.
Notifications will now be fired from the Employer API on changing application/claim items to "New".
Added a NotificationCheck custom component, this will check all current user's notification entries against their BCeID email, only run once per log in, this is situated in the Admin component in App.tsx
On Need Employee Submission, a notification item is sent to the employer stating they have applied.
On Have Employee Submission, a notification item is sent to employees stating the next steps
On all submissions, a notification email is sent to all users with mapping to that Catchment.
Refactored parseCatchments into it's own utils function to be reused.
Updated authProvider functions: checkAuth to use the keycloak instance instead of localStorage.

npham49 commented 11 months ago

For reviewing, please have the following ENVs added:

For Form API: S3_STATIC_IMG_URL=(Link to minio on 551bf1) SP_URL=(Your local SP portal link) EMPLOYER_API_URL=(Your local Employer API link)
For Employer API: FORMS_API_URL=(Your local Form API link)

The ENV change is also reflected in the .env.sample. //TODO: On deployment to Dev, add all envs to deploymentConfig

npham49 commented 11 months ago