FU error handling with the http requests

[cch5ng]

cases:

• [x] after create/edit job form
• [x] after create/edit event form
• [x] after get events request
• [ ] ?after get jobs request? not sure how to handle because that is done in context

[cch5ng]

resc

https://itnext.io/graceful-error-handling-in-rest-driven-web-applications-d4209b4937aa

https://stackoverflow.com/questions/53022281/how-catch-error-in-the-front-end-from-response-of-expressjs

---

https://codeburst.io/error-handling-in-spa-applications-e94c4ecebd86

https://levelup.gitconnected.com/the-definite-guide-to-handling-errors-gracefully-in-javascript-58424d9c60e6

[cch5ng]

https://stackoverflow.com/questions/59180679/update-context-from-another-context-in-reactjs

• simpler to start from Events (CRUD should result in updated alert context)
• messier with Jobs (using jobs-context so how to update context from another context)

[cch5ng]

check https://dev.to/kevjose/building-a-reusable-notification-system-with-react-hooks-and-context-api-2phj

[cch5ng]

X-(actually fixed) think there is some issue with AuthenticatedApp > alertCloseHandler() due to click handler sometimes triggering on the svg vs another element

X-currently there is a workaround for the alert close triggering Events to rerender and run useEffect()

[cch5ng]

current version is not having infinite loop on alert close

issues

• X-styling of alert (should be at top of view, not at bottom)
• X-alert message is not getting rendered
• X-should not require a parent div with specific id any longer

[cch5ng]

issues

• if close alert, then click on page (nav menu), this is re-rendering an triggering duplicate alert (unnec)
• job name field (create form) is not responsive immediately (see if it is some conflict with the nav menu handling)
• the alert icon (left side) looks weird for success, maybe it should be different for success vs error message

https://developer.mozilla.org/en-US/docs/Web/CSS/position#performance_accessibility