Replies: 3 comments
|
Voted ✅ I like the substitution syntax because of how easy it is to see and understand. That said, I also like the |
0 replies
|
Myst role syntax for me! bit more verbose but fits our Myst inspired superset. The substitution syntax is problematic for me scanning wise, it also makes grepping for variables slightly harder. i-prefix, is a bit hard to scan too IMO, |
0 replies
|
We have 4 votes for the substitution-like syntax and 3 votes for the MyST syntax. Since there is no clear winner (just one vote difference), we will probably go with the MyST syntax because there is already a parser for it and plays well with our existing ecosystem. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
We are currently working on a Icons syntax, where you can use EUI icons.
Our initial idea was to use the
:icon-name:syntax, which is known from GitHub or Slack. Unfortunately, this syntax conflicts with our MyST directive syntax.:::{directive} :option: Content :::Hence, we want to know which syntax you would prefer to work with.
Options
MyST syntax
The icon is {icon}`check`.i-prefix syntax
substitution-like
10 votes ·
All reactions