fhir-toolbox-go integration #52
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi @brianpos,
I will give a community talk on our open-source project https://github.com/DAMEDIC/fhir-toolbox-go at the DevDays.
This PR compiles our Go FHIRPath evaluation engine to WASM and adds it as another backend to the Tester.
I am not quite sure how to integrate this into the build process. I see two options:
(could be optional that it builds without
fhir-toolbox-gosupport if no Go compiler is available)just check the compilestatic/fhir-toolbox-go.wasminto the Git repoWhat do you prefer?
Edit: I just integrated the build with the Nuxt build system (using a hook)