Replies: 1 comment
-
Currently, snippets expect block content to be injected. If the snippet content is indented, it intelligently indents the page content, etc. This obviously wouldn't work for inline content. One of the reasons I've left out inline snippet content is that since we are injecting entire pages of content, it doesn't translate as well and would cause many users confusion, and, in turn, cause me many support issues I'd have to answer. So, let's say that when inserting inline we skip indenting the inserting content to work better with inline. Consider the following.
Now I have someone complaining that this doesn't work, and it doesn't work due to the way things are inserted.
This is one of the reasons it is implemented as it currently is. You would really need to devise a whole different approach to how things are done with inline. Currently, snippets is a very simple content insertion extension that is run as a preprocessor (before most Markdown processors run). |
Beta Was this translation helpful? Give feedback.
-
It would be quite nice if snippets could be used inside a line (in-between content), rather than having them on a separate line.
This would allow setups such as this (Assuming this snippet syntax would be used):
This would allow for the version to exist within a separate file that could be updated through certain methods (I.e. some CI tasks to pull data and update the file before docs are build).
Beta Was this translation helpful? Give feedback.
All reactions