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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃悰 Correctly parse tags in {code-cell} #1128
Conversation
Ah nice, this confused me as well. I've added a quick example to document this so that others know how to control it. If that example looks correct to @rowanc1 then I say we merge! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me in the docs!
One thing that's not clear to me (please update if you wanna quickly change this) is how you'd specify multiple tags. E.g. would it be :tags: "one, two, three"
. Or would it be:
:tags:
- one
- two
- three
?
I'll take your word for it on the tests :-D
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops I spoke too soon, it looks like the cells on that page aren't being executed...could this be because {code-cell}
is in a quote block?
They can be comma separated or parsed as yaml:
Or
Right now I think that |
This is a bit of a subtle change that was made is that single line I opted to support the current yaml parsing here to support jupyter-book out of the gate without changes. Maybe that should be under a flag? |
For some reason the execution is still not happening |
I am looking into that now, something to do with the blockquote. |
The bug is here, going to leave that one for a new day: I am going to un-nest this out of the block quote, which works and get this improvement in. :) |
yessss thanks |
This now correctly parses tags for
{code-cell}
directives, and works for visibility. The theme still does not dohide-
butremove-input
,remove-cell
, andremove-output
now all work in markdown notebooks.This means that things like this:
Now show the output nicely in the docs, with the
--execute
flag on. Super cool.cc @choldgraf