Right now, the mystDirectiveError node gets created instead of the directive with a warning.
I think that we should change the logic to still create the correct token, but provide warnings. For example, adding an unknown option to a directive (e.g. with a typo), should still result in that directive node, but perhaps the mistyped option not available in the options and an error raised.
For example, this:
```{admonition} Title
:not-a-prop: value
```
Should parse to a valid admonition, node, rather than a mystDirectiveError, with a warning raised.
This is especially obvious when myst-js has a smaller implementation than a sphinx definition, the markup should parse optimistically and not error at the token phase.
Right now, the
mystDirectiveErrornode gets created instead of the directive with a warning.I think that we should change the logic to still create the correct token, but provide warnings. For example, adding an unknown option to a directive (e.g. with a typo), should still result in that directive node, but perhaps the mistyped option not available in the options and an error raised.
For example, this:
Should parse to a valid
admonition, node, rather than amystDirectiveError, with a warning raised.This is especially obvious when myst-js has a smaller implementation than a sphinx definition, the markup should parse optimistically and not error at the token phase.