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
As You may be aware I'm trying to adopt the Myst AST in papyri, and I'm missing some flexibility in code blocks.
In particular before moving to Myst AST my code block were more structured, and I was able to have links for each token, so that say clicking on array in a code block that contain np.array to open the relevant docs.
Proposal
Do you believe it would make send to have code-block be able to contain a list of children that are inline items instead of a value ? The other things this would allow it to potentially highlight individual token differently, like make some bold and/or and help the syntax highlighting by precomputing it for each token.
Tasks and updates
No response
The text was updated successfully, but these errors were encountered:
Thanks for opening your first issue here! Engagement like this is essential for open source projects! 🤗
If you haven't done so already, check out EBP's Code of Conduct. Also, please try to follow the issue template as it helps other community members to contribute more effectively.
If your issue is a feature request, others may react to it, to raise its prominence (see Feature Voting).
Context
As You may be aware I'm trying to adopt the Myst AST in papyri, and I'm missing some flexibility in code blocks.
In particular before moving to Myst AST my code block were more structured, and I was able to have links for each token, so that say clicking on
array
in a code block that containnp.array
to open the relevant docs.Proposal
Do you believe it would make send to have code-block be able to contain a list of children that are inline items instead of a value ? The other things this would allow it to potentially highlight individual token differently, like make some bold and/or and help the syntax highlighting by precomputing it for each token.
Tasks and updates
No response
The text was updated successfully, but these errors were encountered: