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
Changes to this library (which I'll refer to as ngx-formentry for clarity here) must be kept in lockstep with changes to:
File uploader - an Angular library that the Form Engine consumes to leverage image and PDF upload capabilities.
Form entry app - an Angular library in the O3 Patient Chart that consumes this library.
Housekeeping
ngx-formentry
Per Angular's version compatibility guide, v14 is currently the oldest supported version. Beyond leveraging potential API improvements, migrating Angular to v14 would offer us several immediate benefits, including support for newer TypeScript versions. Most things in the Patient Chart rely on TypeScript versions newer than v4.7. Angular v14.2.x depends on TypeScript versions between the >=4.6.2 <4.9.0 range. Bumping to v14 should help us get closer to a point where we don't need to manage different versions of TypeScript or rely on having resolutions in our manifest files.
Evaluate the feasibility of leveraging Lit Element components as embedded components.
Figure out how to optimally leverage the module federation capabilities of the ModuleFederationPlugin we're using in Patient Chart. The custom webpack config we're using should also be optimized in line with the latest API changes.
Autoscroll to the top of the viewport after clicking on a page in the form UI.
Evaluate the possibility of adding an alternative renderer to the Form Builder that leverages this library.
Develop the next iteration of designs for the form UI.
File uploader
Fix UI issues
Leverage Carbon components
Bug fixes
ngx-formentry
Fix an issue where the custom webpack config in the esm-form-entry app in the Patient chart won't let you run a dev server using yarn serve
Fix an issue where the Combobox / Select and DatePicker Carbon components don't render correctly.
Performance
Investigate issues leading to slow initial load times in the Patient Chart - it appears that these apparent slow downs are primarily owing to network latency.
Testing
Protractor is deprecated. Evaluate Cypress as a replacement. Ultimately, feature work should be backed by a reliable end-to-end test suite.
a11y
Form labels should be accessible.
i18n
Integrate Transifex resources
The text was updated successfully, but these errors were encountered:
gracepotma
changed the title
Technical roadmap
Technical Roadmap for Angular Form Engine
Oct 17, 2023
Preamble
Changes to this library (which I'll refer to as
ngx-formentry
for clarity here) must be kept in lockstep with changes to:Housekeeping
ngx-formentry
Per Angular's version compatibility guide, v14 is currently the oldest supported version. Beyond leveraging potential API improvements, migrating Angular to v14 would offer us several immediate benefits, including support for newer TypeScript versions. Most things in the Patient Chart rely on TypeScript versions newer than
v4.7
. Angularv14.2.x
depends on TypeScript versions between the>=4.6.2 <4.9.0
range. Bumping to v14 should help us get closer to a point where we don't need to manage different versions of TypeScript or rely on having resolutions in our manifest files.Form entry app
File uploader
Updates to the form entry library must be kept in lockstep with the file uploader library.
Feature work
ngx-formentry
File uploader
Bug fixes
ngx-formentry
esm-form-entry
app in the Patient chart won't let you run a dev server usingyarn serve
Performance
Testing
a11y
i18n
The text was updated successfully, but these errors were encountered: