Add workflow for automated deployment#37
Open
pierzchala-m wants to merge 19 commits into
Open
Conversation
f91dad5 to
da10350
Compare
There was a problem hiding this comment.
Pull request overview
This PR updates the repository to support automated deployments to Proxmox via GitHub Actions, and includes a couple of frontend build/integration updates in the fhir-scheduler package.
Changes:
- Switch Proxmox deployment workflow to run on pushes to
mainand adjust deployment inputs for Docker-based runtime. - Update fhir-scheduler components to use
buildQuestionnaireResponsefrom@mieweb/forms-rendererinstead oftoFhirQuestionnaireResponse. - Update demo HTML pages to load
dist/style.cssinstead ofdist/fhir-scheduler.css.
Reviewed changes
Copilot reviewed 1 out of 1 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| packages/fhir-scheduler/src/components/IntakeQuestionnaire.tsx | Switches forms-renderer API usage to buildQuestionnaireResponse. |
| packages/fhir-scheduler/src/components/BookingForm.tsx | Switches forms-renderer API usage to buildQuestionnaireResponse. |
| packages/fhir-scheduler/provider-view.html | Updates stylesheet link to dist/style.css. |
| packages/fhir-scheduler/index.html | Updates stylesheet link to dist/style.css. |
| .github/workflows/proxmox-deploy.yml | Enables auto-deploy on main pushes and updates deployment configuration. |
dfa5d4a to
7ff8953
Compare
a5f4118 to
10bf39c
Compare
…ns answered The "Continue to Provider Selection" button always showed "Please complete all questions before continuing" regardless of answers given. Root causes: 1. QuestionnaireRenderer v2.1.5 does not support the `onChange` or `storeRef` props — both were silently ignored, so completion state was never updated from its initial `false` value. 2. Even when using the internal store, only top-level section objects were checked (not nested question fields inside sections), so the check always evaluated against empty data. Fix: Use the `ref` API (`getResponse()`) that QuestionnaireRenderer v2.1.5 actually exposes. Completion is now evaluated synchronously on button click by reading answered field IDs from the renderer ref, reconstructing field state to evaluate `enableWhen` visibility conditions, and verifying all visible non-section fields have answers. Also unblocks the previously `test.fixme`-marked E2E test that covered the full new-patient questionnaire → booking flow, which is what allowed this regression to go undetected.
|
Preview deployment is ready. URL: https://mieweb-fhirtogether-add-workflow-for-automated-deployment.os.mieweb.org |
40b9e8b to
2aca9a4
Compare
horner
approved these changes
May 19, 2026
…points Agent-Logs-Url: https://github.com/mieweb/FHIRTogether/sessions/5d5f5d9e-465a-4cea-957a-0fe069228762 Co-authored-by: pierzchala-m <162727606+pierzchala-m@users.noreply.github.com>
Contributor
|
Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details. Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
Agent-Logs-Url: https://github.com/mieweb/FHIRTogether/sessions/3733074a-e91f-44af-b9bb-2b2dbdb6c98f Co-authored-by: pierzchala-m <162727606+pierzchala-m@users.noreply.github.com>
Agent-Logs-Url: https://github.com/mieweb/FHIRTogether/sessions/3733074a-e91f-44af-b9bb-2b2dbdb6c98f Co-authored-by: pierzchala-m <162727606+pierzchala-m@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.