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
That's maybe a quite rare thing that we have and I'm not sure we really need it on the new system, but still raising it for awareness:
In asciidoc, some specific syntax without any "source formatting" still gets some formatting applied in the output. This is currently lost in the new system.
See how it displays in the output:
Here we can notice that the 3rd column gets some "input" type of formatting applied. When looking at the sources, there is no specific formatting calling for it.
Expected behavior
Not sure what we'd want to expect from this. The + in asciidoc is that it's able to recognize some specific things like file paths, turn plain URLs into actual links, etc., but on the other hand with the new system the output strictly follows the formatting as it is in the sources, which is actually logical as well.
Steps to reproduce
No response
Tooling
docs-builder
migration tooling
I'm not sure
The text was updated successfully, but these errors were encountered:
Thanks for opening this. Changing to question so we can surface it to other folks.
My opinion is to not support this functionality in V3. I can't figure out exactly why this is happening in the asciidoc build. I want to try to avoid magic like this in V3 so that the syntax always reflects the output.
Describe the bug
That's maybe a quite rare thing that we have and I'm not sure we really need it on the new system, but still raising it for awareness:
In asciidoc, some specific syntax without any "source formatting" still gets some formatting applied in the output. This is currently lost in the new system.
See how it displays in the output:
Here we can notice that the 3rd column gets some "input" type of formatting applied. When looking at the sources, there is no specific formatting calling for it.
Expected behavior
Not sure what we'd want to expect from this. The + in asciidoc is that it's able to recognize some specific things like file paths, turn plain URLs into actual links, etc., but on the other hand with the new system the output strictly follows the formatting as it is in the sources, which is actually logical as well.
Steps to reproduce
No response
Tooling
The text was updated successfully, but these errors were encountered: