You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following up on #21, it would be great if there was some way of annotating cells that are expected to error.
Ideally, the build system would take that to mean that a cell errors if and only if it is annotated as such; if this condition is not met, building the book would fail and we'd get a report showing what went wrong, where.
The text was updated successfully, but these errors were encountered:
Jupyter Book has an option execute: allow_errors that controls whether or not we allow errors to happen.
There is also a tag that we can use to let the build system know that a given cell is expected to error.
Using these two together will likely do the trick. However, for these to work, the Dyalog kernel has to be tweaked so that error outputs are seen as such by the Jupyter interface.
Currently, Dyalog APL errors aren't picked up in the same way as, say, errors in Python notebooks are picked up.
Following up on #21, it would be great if there was some way of annotating cells that are expected to error.
Ideally, the build system would take that to mean that a cell errors if and only if it is annotated as such; if this condition is not met, building the book would fail and we'd get a report showing what went wrong, where.
The text was updated successfully, but these errors were encountered: