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
Hi, many thanks for the library!
Why do we want to catch errors here and here if throwOnError: true is passed — leaving no chance to show error in the UI? I would rather use throw insead of console.logs here and catch error in the outside.
The text was updated successfully, but these errors were encountered:
zackw
added a commit
to zackw/markdown-it-katex
that referenced
this issue
Dec 3, 2022
By default, invoke KaTeX in ‘throwOnError:false‘ mode, so that it will
produce _something_ from any input, and in particular, something which
is guaranteed not to allow any live HTML tags through from the input.
(Unless you are using ‘trust:true‘, in which case you presumably know
what you are doing and why.)
throwOnError:true mode can be re-enabled with plugin options, but then
this plugin will **not** catch any exceptions that are thrown, leaving
recovery up to a higher level.
Since this is a significant behavior change, but one that is more
likely to *fix* bugs in dependent programs than to introce them,
the version number is now 2.1.0.
Fixeswaylonflinn#26, waylonflinn#30, and waylonflinn#7. I would like to thank @khrykin, poster of waylonflinn#7,
for the idea that maybe the exception handlers inside this plugin
should just be completely removed.
Hi, many thanks for the library!
Why do we want to catch errors here and here if
throwOnError: true
is passed — leaving no chance to show error in the UI? I would rather usethrow
insead ofconsole.log
s here and catch error in the outside.The text was updated successfully, but these errors were encountered: