-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
For v3.0.1: indented directive options no longer recognised #922
Comments
Thanks for opening your first issue here! Engagement like this is essential for open source projects! 🤗 |
Heya, ah I think I know why this is, if you have the options without the indentation, it should work, e.g.
let me know? But yeh I can fix this regression (and add a test to catch it 😅) hopefully in the next day or two |
Thanks for the quick response @chrisjsewell, that fixed it!! 😄 Cheers |
Cheers, yeh one of those things where an "implementation detail" becomes part of the spec lol; |
FYI you know you can just surround with more backticks, e.g.
|
Thank you! We're seeing the same issue, with lots of warnings for all the indented options ... |
Awesome, thanks!! |
What version of
myst-parser
are you using?3.0.0
What version dependencies are you using?
What operating system are you using?
Windows
Describe the Bug
In version 2.0.0 I have the images with content (I use backticks in the real version but use
:::
here for formatting reasons), e.g.:but the content is not respected (e.g. image size) and the warning reads:
I checked the changelog and couldnt see anything immediately relevant so listed as bug, but maybe this is a new feature I am misunderstanding.
Expected Behavior
Image formats with content as directed .
To Reproduce
I believe building with any image content should show the error.
The text was updated successfully, but these errors were encountered: