[refactor] error handling ux

[ShaunSHamilton]

Error Kinds

• IPC
• api.freecodecamp.org
• api.github.com (releases json)
• github.com (release assets)

Error Sites

• Splash page
• Login page
• Landing page
• Exam Landing page
• Exam page

Errors by Page

Splash

• IPC
  • check invoke
• api.github.com
  • backend request for releases
• github.com
  • plugin request to download

Login

• IPC
  • keys set/get
• api.freecodecamp.org
  • request to validate token

Landing

• api.freecodecamp.org
  • request exams

Exam Landing page

• N/A

Exam

• api.freecodecamp.org
  • request post attempt

[ShaunSHamilton]

Solutions

Inline

Show an error next to the relevant data on the page.

Example: Splash page fails to download update, an error appears below the list of tasks

Error Page

Redirect the client to the error page to show detailed information.

Flash

Show sticky flash message with error.

Ideal?

Anything that happens on the exam page is destructive. So, there should never be a reason to redirect from that page - all errors should be on-page. All events must be logged to Sentry with attempt information.

Should the error page ever be used?

[ShaunSHamilton]

The error shape should also be designed.

Error Cases

• IPC
  • Mostly determined by:

exam-env/src-tauri/src/error.rs

Lines 10 to 16 in e216d4b

	pub enum Error {
	Credential(String),
	FS(String),
	Serialization(String),
	Request(String),
	Client(String),
	}

• JS Error

Sentry captures Error events as well as transactions.