Discuss error codes instead of just error messages

[plocket]

[Decision: After some research, we'll just use numbers sequentially as we create them.]

Might help to list all the error messages to figure out which codes might be appropriate. Shall we have numbers for types of error codes as well as the specific error itself?

Reasons: This would help us document them and then help devs find their documentation most easily whether or not the text of the error changes. [We would still include the text of the error (a short summary) along with the code.]

Edit:

Brainstorming categories of errors/warnings

Warnings:

• Reference(?)/Missing(?) warning:
  • target var not named on page
  • target var on page not present in story table
  • Unused rows - field/variable not found in run of Story Table
  • value not found in field run of Story Table (possibly unused rows, possibly field found, but value missing)
  • file not found (in sources folder) in Story Table

Errors:

• Syntax/parsing error: cucumber syntax/parsing errors
• Server error: e.g.
  • server reloading (including sign out error)
  • interview not found
  • interview dependency not found (like a missing template)
• ?? error: e.g.
  • could not pull branch during setup
  • ??
• Reference/Value/Missing error: e.g.
  • env var not found
  • phrase not found
  • field/variable not found in linear Step
  • value not found in field in linear Step
  • file not found (in sources folder) in linear Step
• Navigation/Submission error: e.g.
  • "infinite loop" (once we can detect that)
  • (maybe) page context doesn't exist anymore
• Input/Incomplete error: e.g.
  • user couldn't continue (or does this go in navigation error?)

[plocket]

Decision: After some research, we'll just use numbers sequentially as we create them.

[plocket]

We'll also give everything codes, not just errors and warnings - error, warning, info, success, debug. That way they can all be tested appropriately and communicated about more easily.