Closed RieksJ closed 11 months ago
You're correct! The error should not fall back all the way to the instruction, instead it should be recognized that something went wrong while loading a curated text. I've added a try/catch block so a similar error will now look like this, continuing after the error is shown. I've noted this issue so I can correct this in other tools as well if it exists. I still want to go over every possible error case in the near future.
Here is the proof:
The error was caused by the frontmatter having two items called
glossaryTerm
, and has been fixed in the meantime.The bug here is that