Error epic kick off session

[ruthhammond]

Initial team discussion to look at the problem as a whole and the work that may need to be done

[JonJMagee]

Session booked for 07/03/23

[willharrison-madetech]

Hi Jon,

I guess you need to take me off the mailing list?

Will

Will Harrison (he/his) Senior Software Engineer

https://www.madetech.com/?utm_source=signaturesatori&utm_medium=email&utm_campaign=general_signature www.madetech.com https://www.madetech.com/?utm_source=signaturesatori&utm_medium=email&utm_campaign=general_signature twitter.com/madetech http://twitter.com/madetech linkedin.com/company/madetech https://www.linkedin.com/company/madetech/ Making Tech Better podcast https://hubs.ly/H0LhK_n0

On 28 Feb 2023, at 14:36, JonJMagee @.***> wrote:

Session booked for 07/03/23

— Reply to this email directly, view it on GitHub https://www.google.com/url?q=https://github.com/alphagov/govuk-prototype-kit/issues/1909%23issuecomment-1448294105&source=gmail-imap&ust=1678199766000000&usg=AOvVaw1BMZuYH8sm-qm2iWiVKTNe, or unsubscribe https://www.google.com/url?q=https://github.com/notifications/unsubscribe-auth/A5NH2IMDFBAUHRRG7PQFJTDWZYENLANCNFSM6AAAAAAT54YOV4&source=gmail-imap&ust=1678199766000000&usg=AOvVaw01w2Fv8O6jxP9qoRawcCHc. You are receiving this because you are subscribed to this thread.

[JonJMagee]

Oh yes, sorry buddy

On Tue, 28 Feb 2023 at 14:56, Will Harrison @.***> wrote:

Hi Jon,

I guess you need to take me off the mailing list?

Will

Will Harrison (he/his) Senior Software Engineer

< https://www.madetech.com/?utm_source=signaturesatori&utm_medium=email&utm_campaign=general_signature

www.madetech.com < https://www.madetech.com/?utm_source=signaturesatori&utm_medium=email&utm_campaign=general_signature>

twitter.com/madetech http://twitter.com/madetech linkedin.com/company/madetech https://www.linkedin.com/company/madetech/ Making Tech Better podcast https://hubs.ly/H0LhK_n0

On 28 Feb 2023, at 14:36, JonJMagee @.***> wrote:

Session booked for 07/03/23

— Reply to this email directly, view it on GitHub < https://www.google.com/url?q=https://github.com/alphagov/govuk-prototype-kit/issues/1909%23issuecomment-1448294105&source=gmail-imap&ust=1678199766000000&usg=AOvVaw1BMZuYH8sm-qm2iWiVKTNe>, or unsubscribe < https://www.google.com/url?q=https://github.com/notifications/unsubscribe-auth/A5NH2IMDFBAUHRRG7PQFJTDWZYENLANCNFSM6AAAAAAT54YOV4&source=gmail-imap&ust=1678199766000000&usg=AOvVaw01w2Fv8O6jxP9qoRawcCHc . You are receiving this because you are subscribed to this thread.

— Reply to this email directly, view it on GitHub https://github.com/alphagov/govuk-prototype-kit/issues/1909#issuecomment-1448328557, or unsubscribe https://github.com/notifications/unsubscribe-auth/A5Z6GHHSXO5PZYQK72OXAKTWZYG2TANCNFSM6AAAAAAT54YOV4 . You are receiving this because you commented.Message ID: @.***>

[nataliecarey]

Since that kick off I've been thinking about how to break down the tasks. I think it's important that we release in phases, once we have something better than the production version we should release it. My suggestion for how to break this down is:

Phase 1 - quick wins

• Better 404 (not found) pages

• Better 500 (error) pages

  Phase 2 - (concentrating on the technically difficult parts) Live reloading

  • Show a simple 500 (error) page when the server couldn't start
  • Get live reloading working within that error screen
  • Get live reloading working so the error screen appears when there is a problem
  • Get live reloading working so the error screen goes away when the problem is resolved
  • (ideally) Let the user know when the application is attempting to restart

Phase 3 - (concentrating on the technically difficult parts) Non-breaking errors

• When there's a SCSS compilation issue that doesn't stop us from running the kit we should let the user know in the browser
• When there's a client-side Javascript error that doesn't stop us from running the kit we should let the user know in the browser

Phase 4 - Improving error messaging

• Help the user know where the error occurred
  • Showing the contents of the file that has the problem
  • Where possible highlight the line containing the problem
  • Explain whether this error occurred in their code, in a plug-in, in the kit itself
• Explain 10 different error messages (ones that we identify as common)

Phase 5 - Finishing touches

• Help the user to communicate these errors to others (e.g. "share this error" button)
• (I'm sure we'll have more by this point)