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
{{ message }}
This repository has been archived by the owner on Sep 5, 2023. It is now read-only.
Syntax markup gets messed up after a field with a name type, followed by optional is used.
Expected Behavior
type and the below fields should be displayed constantly.
Current Behavior
type and the below fields are not displayed constantly.
Steps to Reproduce
Paste the following concept into the editor:
concept Foo {
o String bar optional
o String type optonal
o String Baz optonal
}
Desktop
OS: macOS 12.1
The text was updated successfully, but these errors were encountered:
stefanblaginov
changed the title
Syntax markup gets messed up after a field with a name "type", followed by "optional" is used
Bug: Syntax markup gets messed up after a field with a name "type", followed by "optional" is used
Jan 31, 2022
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Syntax markup gets messed up after a field with a name
type
, followed byoptional
is used.Expected Behavior
type
and the below fields should be displayed constantly.Current Behavior
type
and the below fields are not displayed constantly.Steps to Reproduce
Paste the following concept into the editor:
Desktop
The text was updated successfully, but these errors were encountered: