-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lower case v causes error in the parser #108
Comments
updated to say any "v" in spec causes an error |
Fixed the problem, it will be included in the next release. Root cause was that the character v is also used for direction down |
I see the fix and the test passes. However, this |
Missed this one or I would have included this in 0.3.3. I have added v as a valid for ids so with the next release this will work. Perhaps we should sum things up and do bigger fix for the characters. Right now its one at a time when they pop up. |
The wiki should be updated to reflect that direction of graph can also be specified by >,<,^,v. |
This si working in the mermaid version 0.4.0. Closing this issue. Reopen if this till is a problem. |
Sorry to be a pain, but...
Not really a huge problem, but |
I agree, will look at it. It is a "keyword" but perhaps the grammar could allow this keyword. |
…ontawesome_stylesheet Updated fontawesome stylesheet link
It appears
v
anywhere inside the diagram spec will cause the parser to fail. As an example,graph LR; v;
fails whilegraph LR; V;
works just fine.ref rich-iannone/DiagrammeR#47
The text was updated successfully, but these errors were encountered: