Skip to content
This repository has been archived by the owner on Sep 5, 2023. It is now read-only.

Bug: Syntax markup gets messed up after a field with a name "type", followed by "optional" is used #109

Open
stefanblaginov opened this issue Jan 31, 2022 · 0 comments

Comments

@stefanblaginov
Copy link

Syntax markup gets messed up after a field with a name type, followed by optional is used.

Screenshot 2022-01-31 at 14 31 30

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
@stefanblaginov 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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant