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
Transferred from internal JIRA issue originally created 2020-12-15.
Right now, we hardcode the SUSHI version that FSH Online is using. We may be able to use pre- or post- build steps to do this. From Chris when discussing this originally on the pull request:
The SUSHI version is known at build-time. I think we could find a way to inject it into the code during the build - so it's not hard-coded in our source, but looks hard-coded in the output. I'm thinking we could do that as a post-build script that does a replacement in the output file or maybe use custom environment variables--maybe setting the SUSHI number programmatically as an env variable in a pre-build step... Anyway, I'm not sure the most elegant approach, and I don't think it has to be figured out in this PR, but I suspect we can come up with something.
BTW, I think we could pull the SUSHI version from the package-lock.json (but again, this would need to be handled during build rather than during runtime).
The text was updated successfully, but these errors were encountered:
Transferred from internal JIRA issue originally created 2020-12-15.
Right now, we hardcode the SUSHI version that FSH Online is using. We may be able to use pre- or post- build steps to do this. From Chris when discussing this originally on the pull request:
The SUSHI version is known at build-time. I think we could find a way to inject it into the code during the build - so it's not hard-coded in our source, but looks hard-coded in the output. I'm thinking we could do that as a post-build script that does a replacement in the output file or maybe use custom environment variables--maybe setting the SUSHI number programmatically as an env variable in a pre-build step... Anyway, I'm not sure the most elegant approach, and I don't think it has to be figured out in this PR, but I suspect we can come up with something.
BTW, I think we could pull the SUSHI version from the package-lock.json (but again, this would need to be handled during build rather than during runtime).
The text was updated successfully, but these errors were encountered: