FHIR Chat · sushi 1.3.1: single quotes needed? · shorthand

Stream: shorthand

Topic: sushi 1.3.1: single quotes needed?

Patrick Werner (Apr 05 2021 at 14:05):

I'm not 100% sure if this was introduced by sushi 1.3.1 or is it just me.
I'm getting errors on lines like this:
* authorizingPrescription.identifier[+].value ="160.123.456.789.123.58"

Patrick Werner (Apr 05 2021 at 14:07):

 extraneous input '160.123.456.789.123.58"' expecting {<EOF>, KW_ALIAS, KW_PROFILE, KW_EXTENSION, KW_INSTANCE, KW_INVARIANT, KW_VALUESET, KW_CODESYSTEM, KW_RULESET, KW_MAPPING, KW_LOGICAL, KW_RESOURCE}
  File: /Users/patrickwerner/IdeaProjects/eRezeptAbgabedaten/examples-fsh/input/fsh/example-KBV-PZN.fsh
  Line: 46

Jose Costa Teixeira (Apr 05 2021 at 14:07):

sushi needs spaces after the =, did you try that?

Patrick Werner (Apr 05 2021 at 14:11):

yes (removed the space by accident while copying to zulip)

Patrick Werner (Apr 05 2021 at 14:12):

minimal example works: https://fshschool.org/FSHOnline/#/share/3mk57uJ

Jose Costa Teixeira (Apr 05 2021 at 14:16):

(btw, @Chris Moesel sushi needs spaces after the =...)

Jose Costa Teixeira (Apr 05 2021 at 14:17):

@Patrick Werner What's broken then? In the example you gave it seems fine..

Patrick Werner (Apr 05 2021 at 14:17):

will dig deeper and try to isolate the issue

Patrick Werner (Apr 05 2021 at 14:21):

i'm confused by the outputextraneous input '160.123.456.789.123.58"' only showing a single double quote at the end

Patrick Werner (Apr 05 2021 at 14:21):

If i'm removing the first double quote the error disappears: * authorizingPrescription.identifier[+].value = 160.123.456.789.123.58"

Patrick Werner (Apr 05 2021 at 16:36):

ahhh! I found double quote further up in the fsh file which shouldn't be there

Patrick Werner (Apr 05 2021 at 16:37):

my bad

Patrick Werner (Apr 05 2021 at 16:38):

Related to this issue: are there any plans on FSH syntax highlight support for IntelliJ?

Chris Moesel (Apr 06 2021 at 19:01):

1. We've looked into making spaces around = optional, but it is surprisingly more tricky than you would think. Every once in a while we bring it back up in our backlog, re-evaluate it, and then end up de-prioritizing it again. We haven't yet decided not to do it, but we also haven't yet been able to justify the time, effort, and havoc it would wreak on our formal grammar.

2. At this point, we're only invested in supporting FSH on VS Code. We've had requests to support it in other editors (including Notepad++, Atom, and now IntelliJ), but so far we do not have any plans to do so. If someone else wants to give it a shot, we're glad for them to take it on!

Last updated: Apr 12 2022 at 19:14 UTC