OHS-Hosting-Infrastructure / complaint-tracker

**This repo is currently not in active development.** Increasing visibility into complaint status by connecting data across the OHS ecosystem
Other
4 stars 0 forks source link

Ensure we can access the session user details #200

Closed rahearn closed 2 years ago

rahearn commented 2 years ago

Description of change

Nested hashes in session have only string keys by default when reloaded from the cookie. This change ensures that we can access the data we need

Paired with @jduss4 on the solution.

Acceptance Criteria

Before the change: complaints were not loading from HSES staging After the change: complaints are loading from HSES staging

Issue(s)

Checklist

To be completed by the submitter:

To the Reviewer

This project is using Conventional Comments to give structure and context to PR comments. Please use these labels in your comments.

github-actions[bot] commented 2 years ago
Pa11y testing results ```yarn run v1.22.17 $ pa11y-ci Running Pa11y on 4 URLs: (node:3244) UnhandledPromiseRejectionWarning: Error: Page crashed! at Page._onTargetCrashed (/home/runner/work/complaint-tracker/complaint-tracker/node_modules/puppeteer/lib/Page.js:215:24) at CDPSession. (/home/runner/work/complaint-tracker/complaint-tracker/node_modules/puppeteer/lib/Page.js:123:56) at CDPSession.emit (events.js:400:28) at CDPSession._onMessage (/home/runner/work/complaint-tracker/complaint-tracker/node_modules/puppeteer/lib/Connection.js:200:12) at Connection._onMessage (/home/runner/work/complaint-tracker/complaint-tracker/node_modules/puppeteer/lib/Connection.js:112:17) at WebSocket. (/home/runner/work/complaint-tracker/complaint-tracker/node_modules/puppeteer/lib/WebSocketTransport.js:44:24) at WebSocket.onMessage (/home/runner/work/complaint-tracker/complaint-tracker/node_modules/puppeteer/node_modules/ws/lib/event-target.js:120:16) at WebSocket.emit (events.js:400:28) at Receiver.receiverOnMessage (/home/runner/work/complaint-tracker/complaint-tracker/node_modules/puppeteer/node_modules/ws/lib/websocket.js:789:20) at Receiver.emit (events.js:400:28) (Use `node --trace-warnings ...` to show where the warning was created) (node:3244) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:3244) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. > http://localhost:8080/grantees/12345 - 0 errors > http://localhost:8080/complaints/pa11y-id - 0 errors > http://localhost:8080/complaints - 0 errors > http://localhost:8080 - Failed to run Errors in http://localhost:8080: • Error: Pa11y timed out (30000ms) ✘ 3/4 URLs passed error Command failed with exit code 2. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. ```