CAN should fire a SCRATCHFILE_ERROR event if unsupported syntax is found

CAN should parse the scratchfile when it is updated. If CAN hits an error in the scratchfile or finds unsupported syntax (CAN uses a subset of markdown), it should fire a SCRATCHFILE_ERROR event with the error passed as an argument. To allow other parts of the software to respond.

Backlinks

• CAN should parse the scratchfile when it is updated
  • CAN should fire a SCRATCHFILE_PARSED event when the scratchfile is parsed. CAN should fire a SCRATCHFILE_ERROR event if unsupported syntax is found. This could be an error in the parsing step (CAN will use remark to process markdown) or markdown that CAN does not explicitly support - CAN notes are written in a subset of markdown. When a SCRATCHFILE_ERROR is emitted, CAN should inform the user
• CAN should fire a SCRATCHFILE_PARSED event when the scratchfile is parsed
  • If the parsing is not successful, CAN should fire a SCRATCHFILE_ERROR event.
• When a SCRATCHFILE_ERROR is emitted, CAN should inform the user
  • CAN should fire a SCRATCHFILE_ERROR event if unsupported syntax is found. When this happens, the user should be informed. For now, CAN should simply print the error with some context 'parsing scratchfile failed'.