Hi @sunbiz@namratanehete small update from my side: I’ve finished the Export JSON work for the form designer. The current designer state can now be exported as FHIR Questionnaire JSON, and I also added basic tests to cover the export structure, nested groups, choice answer options, and invalid enableWhen filtering. I also cleaned up the preview so the JSON shown in the UI matches the exported output more closely.
I had one issue during the UI update where the page briefly stopped rendering, but that’s fixed now and the demo is loading properly again. The export button is visible in the form designer, and the output is being displayed directly in the interface, so it’s much easier to verify than before.
Next I’m planning to continue with the designer workflow improvements and make the conditional logic editing a bit smoother.
Hi @sunbiz, quick update MR !155 (drag-and-drop reordering via SortableJS) has addressed all your review feedback — DOM/Lit desync fix, lazy Sortable init, drag handle, dependency cleanup, and tests for handleDragReorder. Robby flagged that the MR needs to run on an org branch instead of my fork for CI runners, so I’m moving it over now.
Hi @sunbiz , i hope you are doing well. There is GSoC final submission opens in 10 days (Aug 17), so I wanted to align with you now on scope and the work product before I will write.
So far, three MRs merged before the midterm evaluation. After that, four form-designer MRs were also merged :
Add FHIR Questionnaire canvas, import/export, and item actions (!153)
Add lh-form-designer to polymer fragments (!154)
Drag-and-drop canvas with group reordering (!156)
Preview Mode with enableWhen conditional logic (!159)
Export/import panel toggle for FHIR Questionnaire JSON (!160)
Canvas/properties-panel component split (!158)
I am currently finishing the validation-rules work. It includes required fields, min/max length, regex validation, numeric and date ranges, live validation errors in Preview Mode, accessible error messages, and tests.
For the next steps, I was thinking of working on:
Keyboard accessibility and improving the ARIA support
Built-in templates for common forms
Extending the conditional-logic support if needed
Comprehensive documentation and a final demo/report
Given the time left, I want to confirm priorities with you:
Should I prioritize a live GitLab Pages demo and documentation over the remaining stretch features, since the final submission needs to clearly show working code?
Is the validation-rules MR the last major feature you want before I switch fully to documentation and the final report?
Could you please let me know if this order makes sense, or if you would prefer me to focus on something else before the final evaluation?
Hi @Sujal_Co , good progress, thanks for laying it out.
Skip the Pages demo. The CI already deploys from master and is live at
/demos/lh-form-designer.html. Just exercise the deployed page
end-to-end and fix anything that only works in the dev server.
Please prioritize documentation.
Validation rules is the last feature, with one exception: keyboard
and ARIA. That isn’t a afterthought. The designer UI has no roles,
no tabindex, no keydown handlers, and the properties-panel labels
aren’t tied to their inputs, so the authoring surface is unusable
without a mouse. Preview mode already gets
label/for right, so this is scoped to canvas + properties panel.
Revised order:
Validation rules MR, open by Aug 10
Keyboard + ARIA MR, open by ~Aug 13 (keyboard reorder, label
association, focus management.)
Small docs MR: package README with the event contract, and fix
package.json (still says “minimal exploratory”, v0.0.1, test
script exits 1)
Report + demo in the last 2-3 days
Drop templates and further conditional logic.
Note that work counts when merged, not when opened. Anything in review
on Aug 17 won’t make the work product. And generate the MR list from git
log for the report; your message says four post-midterm MRs, lists six.