This log documents significant changes for @aehrc/smart-forms-renderer's alpha releases. This project follows Semantic Versioning.
This changelog only includes changes from version 1.0.0-alpha.1 onwards. For stable releases, refer to the main CHANGELOG.md.
WARNING: Alpha releases are not stable and may contain breaking changes. Changes are also most likely to be undocumented.
- Added meta.tag.system to extracted bundle.
(WARNING: Major breaking changes with library API)
This library API change will be reflected in the next stable release (1.0.0).
A migration guide is provided at MIGRATION-v1.0.md.
buildForm()anduseBuildForm()now accept aBuildFormParamsobject instead of multiple parameters.- The
additionalVariablesparameter is replaced withadditionalContext. Its usage remains the same - it is used to inject additional fhirPathContext variables. - A new library function
repopulateForm()is added to repopulate the form with a new QuestionnaireResponse and/or additionalContext while preserving the current Questionnaire state. Its parameters are defined in the interfaceRepopulateFormParams.
-
If you were previously calling
QuestionnaireStore.setPopulatedContextto inject populatedContext into the renderer, you no longer need to do so.buildForm(),useBuildForm()andrepopulateForm()will take care of it for you via theadditionalContextparameter. -
For pre-population/re-population, you do not need to call
QuestionnaireStore.updatePopulatedPropertiesandQuestionnaireResponseStore.setUpdatableResponseAsPopulatedanymore. Both of these functions are now removed.buildForm(),useBuildForm()andrepopulateForm()will take care of it for you.- // Remove these lines - const updatedResponse = await updatePopulatedProperties(populatedResponse, populatedContext); - setUpdatableResponseAsPopulated(updatedResponse); - - if (populatedContext) { - setPopulatedContext(populatedContext, true); - } + // Re-run buildForm (or repopulateForm) with the new populatedResponse + await buildForm({ + questionnaire: sourceQuestionnaire, + questionnaireResponse: populatedResponse, + terminologyServerUrl: defaultTerminologyServerUrl, + additionalContext: populatedContext + }); -
QuestionnaireStore.populatedContextandQuestionnaireStore.setPopulatedContextare replaced withQuestionnaireStore.additionalContextandQuestionnaireStore.setAdditionalContextrespectively. You most likely won't need to callsetAdditionalContextmanually. -
It is still recommended to create your own wrapper function that calls
destroyForm()to clean up states when the form is unmounted before callingbuildForm()again.async function resetAndBuildForm(params: BuildFormParams) { // Destroy previous questionnaire state before building a new one destroyForm(); // Build new questionnaire state await buildForm(params); }
RendererStylingStoreand interfaceRendererStylingare replaced withRendererConfigStoreandRendererConfigrespectively. This is purely a naming change.rendererConfigOptionscan now be passed into the renderer viabuildForm()anduseBuildForm(). You no longer need to callsetRendererConfigStoremanually.
useStringCalculatedExpressionanduseCodingCalculatedExpressionhooks are removed. CalculatedExpressions are now triggered via an internal task queue. If you are using these hooks in a component override, you can remove the hook safely.objectIsCodinglibrary function is removed.
- Added debouncing to open-choice autocomplete input fields to reduce the number of QuestionnaireResponse updates.
- Reverted changes in 1.0.0-alpha.57 where inline validation messages are shown when the field loses focus. Now inline validation messages are shown immediately when the field value changes (default MUI behaviour).
- Added pre-filtering
cleanDeepcleaning step to ensure empty object values are not included in the extracted bundle. See #1621 (comment) for more details.
- Very minor change where interface are exported as types to align with TypeScript best practices.
- Replaced
typeslice with proposedpatchRequestUrlsub-extension with temporary custom extensionhttps://smartforms.csiro.au/ig/StructureDefinition/TemplateExtractExtensionPatchRequestUrlfor PATCH request support. - See https://chat.fhir.org/#narrow/channel/179255-questionnaire/topic/.24extract.20using.20templates/with/542442943 for more details.
- Bumped version because previous version 1.0.0-alpha.106 wasn't published with the fix.
- Fixed an issue where the asterisk colour is hardcoded as "red" instead of referencing the main error colour of the theme palette.
- Reduce false positives for "alert(" and similar variants when sanitising input fields (from 1.0.0-alpha.98).
- Added support for injecting
aria-labelat item labels, display items, and tab buttons via a custom extension 'https://smartforms.csiro.au/ig/StructureDefinition/QuestionnaireItemTextAriaLabelExpression'. See #1578 for more details.
- Fixed an issue where unmodified items appearing in extract when "add" operation is used.
- Fixed an issue where extracted bundle has additional erroneous value.
- Both issues are from #1594.
- Fixed an issue where the Time item is failing pre-population.
- Resolved an dependency import issue with @aehrc/testing-toolkit where it was not published on NPM. It it used for Storybook-based testing, and now it is now included in the renderer package instead of a separate package.
- Added support for SDC extension http://hl7.org/fhir/uv/sdc/StructureDefinition-sdc-questionnaire-width.html (both % and px) in gtable and grid groups itemControls.
- Fixed an issue where "Clear" buttons in open-choice components do not clear openLevel input fields.
- Fixed an issue where the date input in DateTime items are failing pre-population.
- Added input sanitisation in renderer input fields. See #1533 for more details.
- Changed item-level repopulate button custom extension to the below. See https://chat.fhir.org/#narrow/channel/179255-questionnaire/topic/Granular.20Repopulate.20button/with/533937578 for more details.
{
"url": "https://smartforms.csiro.au/ig/StructureDefinition/questionnaire-initialExpression-repopulatable",
"valueCode": "manual"
}- Added support for an item-level repopulate button via a custom extension 'https://smartforms.csiro.au/ig/StructureDefinition/questionnaire-initialExpression-showRepopulateButton'. This button can only be used on string, text, integer and decimal fields, and cannot be used in repeating items or groups.
- Fix $extract filtering logic when comparing extracted resource with comparison resource (for modified-only usage). Fixed #1507.
- Various TypeScript-related bug fixes.
- In the autocomplete component, when the input is less than 2 characters, an info icon will be displayed at the right end.
- Add enableColorScheme at ScopedCssBaseline for native light/dark alignment with parent app i.e. native scrollbars, native focus rings, etc.
Note that this doesn't provide you with dark mode. for that, you need to wrap
<BaseRenderer>with your own light/dark-mode enabled<ThemeProvider>. See https://mui.com/material-ui/customization/theming/ for more details.
- Remove MUI GlobalStyles (which overrides the parent app) with ScopedCssBaseline in RendererThemeProvider. This sets a baseline for the renderer's MUI styles without affecting the parent app's styles.
- Changed "questionnaire-item-text-hidden" custom extension to use the "https://smartforms.csiro.au/ig/StructureDefinition/<extension_name>" convention. Affected extensions:
- Added backwards compatibility for custom extensions defined in Smart Forms. Both URLs "https://smartforms.csiro.au/ig/StructureDefinition/<extension_name>" and "https://smartforms.csiro.au/docs/custom-extension/<extension_name>" will work for the custom extensions listed below.
- Handle axios-based FetchResourceCallback calls correctly, for both happy and sad paths (res.data).
- Fix TypeScript issues in type predicates.
- When resolving subquestionnaire canonical URLs, enforce in the root questionnaire (returns OperationOutcome if not present), otherwise if it's a recursive resolution within subquestionnaires (for sub-subquestionnaires), be more lenient by returning an empty array.
- Remove Iconify dependency and replaced them with MUI icons. This affects the next/previous tab and page buttons.
- Allow handling of non-Error exceptions when evaluating FHIRPath expressions. Reason: fhirpath.js might not type exceptions as Error objects correctly.
- Updated sdc-populate to v4.6.2. Changes as follows:
- Make error handling in fhirpath evaluations more lenient (remove e instanceof Error check), due to fhirpath.js async evaluation returning a string error message instead of an Error object which results in the error being muted on development builds (surprising it works on production).
- Remove unnecessary (or even wrong) client-side sorting based on effectiveDates and recordedDate in Observation and Conditions respectively.
- Reduce bundle size by removing tests and tets data from published package.
- Add support for custom
https://smartforms.csiro.au/ig/StructureDefinition/GroupHideAddItemButtonextension to hide the "Add Item" button in a repeating group or group table item. This extension is used when you want to prevent users from adding items to a group, but still want to allow them to edit existing items.
- Resolves an issue where the
useValidationFeedbackhook was incorrectly falling back to a generic error message in a required item and whenrequiredItemsIsHighlightedis false.
- Fixed number of columns shown and widths when a grid group has a hidden item.
- Standardise generic
StandardTextFieldto accommodate multiline inputs - so that all fields have the same height. This fixes an issue where adding multiline support (in alpha.82) in text-based fields increases their height. - Added multiline support to dropdown fields too.
- Reverted visual expression update animations to the previous behaviour (Last change was in 1.0.0-alpha.81).
- Add check for falsy input values in calculatedExpression hook updates to prevent unintended visual calculatedExpression updates when nothing has actually changed.
(WARNING: Possible breaking changes with QuestionnaireStore.itemTypes)
- Refactor QuestionnaireStore itemTypes to itemMap. Changed from <linkId, qItem.type> to <linkId, Omit<QuestionnaireItem, 'item'>.
- Refactor
useValidationFeedbackto rely entirely on the QR store’s invalidItems, resolving timing mismatches between inline feedback and global validation state. - For DateTimeItem and QuantityItem, fix an issue where feedback was always shown — now only shows feedback when
showFeedback=true(triggered by unfocusing the field). - When processing target constraints, add a step to filter out invalidItems whose qItem is hidden via questionnaire-hidden or enableWhen.
- Updated sdc-populate to v4.6.0. Changes as follows:
- Add fhirContext handling when creating $populate input parameters.
- Increase tolerance of isLaunchContext() so that it can handle more launch contexts beyond the ones defined in https://hl7.org/fhir/uv/sdc/ValueSet-launchContext.html.
- Add timeoutMs parameter to populateQuestionnaire() input parameters.
- Add multiline support to non-numeric text field-based components. This allows text to auto-wrap when it exceeds the width of the text field.
- Added support for calculatedExpressions to
dateanddateTimeitems.
- Show date and dateTime error messages when parent group is a gtable/grid.
- Due to space constraints for textfield-based items in gtables/grids, expression update animations for textfield-based items are now changed to a faint green glow. Animations are unchanged for radio and checkbox items.
(WARNING: Possible breaking changes with Questionnaire definitions)
- Changed all instances of custom extensions to use the "https://smartforms.csiro.au/docs/custom-extension/*" convention. Affected extensions:
- Added support for new custom extension
https://smartforms.csiro.au/docs/custom-extension/questionnaire-item-text-hiddento prevent rendering of item.text in the renderer. This extension is used when you want to specify item.text for metadata purposes but do not want it displayed in the rendered form.
- Allow
getFhirPatchResourceDisplay()to support non-Bundle resources e.g. patient, user, encounter etc from launch context.
(WARNING: Possible breaking changes)
- Removed all usages of
showMinimalView.
- Added support for renderer-styling usage in Grid tables.
- Updated sdc-populate to v4.5.0. Changes as follows:
- Add display element to
QR.subjectandQR.author.
- Added parseFhirDateTimeToDisplayDateTime() as a library function that parses a FHIR dateTime to a human-readable format.
- Updated sdc-populate to v4.4.0. Changes as follows:
- Add support for child items consuming itemPopulationContext to access fhirPathContext.
- Changed how re-population works:
- Grid items are now re-populated one by one like regular items instead of being repopulated as a whole.
ItemToRepopulateinterface now containssectionItemText(replacesheading),parentItemTextandisInGrid. Items in a grid usually have their item.text as column headings e.g. Value, Date recorded which does not provide much context. In this case,parentItemTextcan be used to provide more context for the item being re-populated.- A new library function
isItemInGrid()is added to check if an item is in a grid (if any of its ancestors is a grid item).
- Fix an issue where invalidItems not updated immediately when target constraint is unmet.
- Fix an issue where in the Playground, existing RendererStylingStore state is wiped (and reverts to the default values) when a button that calls
setRendererStylingStore()is clicked.
- Added getItemTerminologyServerToUse() as a cleaner way to an item to decide which terminology server to use.
- UseQuantityCalculatedExpression() hook now takes into account preferredTerminologyServer when looking up ucum-units.
- Added observation-based extraction helper functions canBeObservationExtracted() and buildBundleFromObservationArray() as library functions.
- Added support for answerOptionToggleExpression in answerValueSet dropdowns.
- Fixed an issue where cursor is not set to "default" when hovering over HTML-readonly checkbox labels
- Fixed an issue where
readOnlyVisualStyleis set to "readonly", radio and checkbox inputs are not truly disabled when they are disabled via answerOptionsToggleExpressions.
- Move dayjs.extend() localisation and parse format functions to BaseRenderer.tsx so they are immediately invoked.
- In non-repeating QuestionnaireItems, strictly only populate one answer (the first answer), even if initialExpression evaluates to multiple answers.
- Fixed an issue where Observation-based extraction is mapping QR.author to Obs.author (should be Obs.performer).
- Fixed an issue where empty strings in text-based fields are passing validation.
- Fixed an issue where items with dynamicValueSets with expansion coding of 0 will trigger a fallback expansion against their qItem.answerValueSet.
- Fixed an issue where decimal, dateTime, slider, radio button items are not taking up full space in a grid table.
- Added ARIA attributes to various components.
- Updated various components to have a more descriptive ARIA label.
- Various fixes to typography to meet accessibility requirements - font size, font color changes
- Augment XHTML renderings (from Questionnaire definition) by adding
altattribute totags.
- Updated MUI component code segments that will be deprecated soon i.e. updated to slotProps.
- Removed
simplebar-reactdependency and all associated custom scrollbar components (Scrollbar.tsxandScrollbar.styles.ts). UpdatedDashboardNavto use native scroll behavior instead. - Downgraded
react-router-domfrom version7.2.0to6.11.2becauseuseBlockeris broken in the later versions.
- Changed how additionalVariables in buildForm() (and it's variants) work. Instead of <name, extension obj> which doesn't provide much value,
it now works more like a fhirPathContext <name, value> where
valueis the evaluated value from fhirpath.evaluate(). additionalVariables likely will come from a pre-population module (like sdc-populate) which then can be injected into the renderer's fhirPathContext.
- Fixed an issue where cqfExpressions are not evaluated when the QuestionnaireResponse is first initialised.
- Changed how additionalVariables in buildForm() (and it's variants) work. Instead of <name, extension obj> which doesn't provide much value,
it now works more like a fhirPathContext <name, value> where
valueis the evaluated value from fhirpath.evaluate(). additionalVariables likely will come from a pre-population module (like sdc-populate) which then can be injected into the renderer's fhirPathContext.
- Fixed an issue where group table cells content is not centre-aligned.
- Added "X" clear buttons to text-based input fields, update renderer to alpha.62.
- Fixed an issue where items in a group table cell doesn't use all available space.
- Centred group table headers.
- Fixed colour differences between readOnly and editable text-based input fields.
- Fixed an issue where group table and grid child items can be edited even when the parent group is readOnly.
- Removed add, remove, drag, check interactions for readOnly group tables.
- Prevent rendering of "Clear" button for radio and checkbox items when they are readOnly.
- Centred cell content in group table and grid table.
- Changed all usages of MUI LoadingButton to Button - see https://mui.com/material-ui/migration/upgrade-to-v6/#button-with-loading-state.
- Fixed an issue where "sparsity" of grid group cells doesn't work as expected.
- CSS read-only (different from Questionnaire item.readOnly) text-based input items now have cursor set to
default.
- Fixed number of columns shown and widths when a group table has a hidden item.
- Updated sdc-populate to v4.3.0. Changes as follows:
- Fixed an issue where a repeating group using ItemPopulationContext only looks at the first item in the group to determine the itemPopulationContext used.
- Included author and authored property when creating a QuestionnaireResponse.
- Changed inline validation messages to be shown when the field loses focus. See issue.
- Exposed getSectionHeading() as a library function
- Use fast-equals deepEqual() instead of lodash.isEqual() for better performance.
- Updated @aehrc/sdc-populate to 4.1.0. It now uses the same removeEmptyAnswers() implementation as the renderer, which is more battle tested.
- Dynamic _answerValueSet options now updates consistently.
- Whenever dynamic _answerValueSet options change, the item fields is now cleared consistently.
- Support for dynamic _answerValueSet in choice and open-choice items. Allows a dynamic answerValueSet URL that dynamic updates the answer options.
- Use individual MUI icon imports in ChoiceAutocompleteField.tsx and ChoiceAutocompleteField.tsx.
- Added support for answerOptionToggleExpressions.
- Added partial support for the facing sync icons when expressions are updated in choice/open-choice checkboxes and radio buttons e.g. dynamicValueSets, answerOptionToggleExpressions.
- Refactored a bunch of choice/open-choice checkboxes and radio buttons to make them cleaner and reduce code duplication.
- Fixed an issue where the initial QuestionnaireResponse has empty
itemarrays ingroupitems. This was causing client-side and server-side validation errors.
- Added partial accessibility support for checkboxes and radio buttons, notably:
- Read-only elements with role="radiogroup" be given aria-readonly="true"
- Checkboxes has role="checkbox" and if they are read-only elements, aria-readonly="true" as well.
- Prevent the cursor from changing to "pointer" when read-only checkboxes and radio buttons are hovered, ripple effects on interaction are also removed.
- Item labels now have
idof'label-' + qItem.linkId. - Checkbox FormGroups and RadioGroups have
aria-labelledbyset to the item label id.
Note: this version doesn't build properly, use v1.0.0-alpha.48 instead.
- Fixed an issue where open-choice dropdown items do not properly capture the value of the selected option. See commit fc0e1a1.
- Use
<div>or<span>tags to all MUI Typography instances, so they won't be renderer astags. Some apps might apply CSS styles to
tags that will affect their rendering.
- Fixed an issue where quantity unit and comparator dropdown fields are bugging out in read-only mode.
(WARNING: Possible major breaking changes with MUI, MUI theming, Tanstack React Query, SDC-Populate, SDC-Assemble)
Changed (See #1182 (comment))
- Upgraded to Material-UI v7. Follow the migration guide to update your MUI to v7. Grid is especially one to pay attention to.
- Upgraded to React Query v5. Follow the migration guide to update your React Query to v5.
- All peer dependencies have become dependencies except for
reactandreact-dom. See #1179. This is because Angular and Vue apps consuming this library do not usually have React-specific libraries like MUI or React Query. - Only supports React 18 and React 19 officially. It might work on React 17, but you might need to do
npm i --legacy-peer-depsornpm i --force. - SDC-Populate and SDC-Assemble interface changes:
FetchResourceCallback,FetchTerminologyCallback,FetchResourceRequestConfig,FetchTerminologyRequestConfig. - It is now a requirement for
FetchResourceRequestConfigto have a sourceServerUrl as the FHIR server URL to fetch resources from. - It is now a requirement for
FetchTerminologyRequestConfigto have a terminologyServerUrl as the FHIR Terminology server URL to fetch terminology from.
- Revert non-readOnly text-based fields to old border colour (MUI default grey-ish).
- Capped peer React version at ^18.0.0. Reason being there are multiple dependencies that are not compatible with React 19.x.x.
- When reading XHTML class styles, skip stylesheets from other origins
- Added support for HTML readonly
attributeas an alternative todisabledfor readOnly items. See https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/readonly#attribute_interactions for more information. - You can toggle between these two visual styles/behaviours via the
readOnlyVisualStyleconfig inRendererStylingStore.
- Completely refactored removeEmptyAnswers() implementation to work with repeat groups.
- Add support for repeat groups in initialisation of calculatedExpressions.
- Add support for class-based styles for XHTML item._text. See #1120 (comment) for more information.
- Fixed an issue where display instructions persists even when the item has an error message.
- Fixed an issue where SDC itemControl
collapsibledoesn't work with Group Table.
- Implement Parameterised/Dynamic ValueSets
- Proposal: https://build.fhir.org/ig/FHIR/fhir-tools-ig/parameterized-valuesets.html
- chat.fhir.org channel: https://chat.fhir.org/#narrow/channel/179202-terminology/topic/Parameterised.20ValueSets/with/509420458
- Implement partial support for header and footer itemControls - header and footer will render properly but will not be sticky.
- Allow two methods for defining SDC itemControl
page:- Standards-based as defined in SDC: https://hl7.org/fhir/extensions/CodeSystem-questionnaire-item-control.html#questionnaire-item-control-page
- Backwards-compatible way - using it as a "page-container"
- Allow
extensionproperty in valueCodings i.e.ordinalValueextension usage.
- Fixed an issue where SDC itemControl
collapsible'sdefault-openvalue doesn't work as expected.
- Add support for when a form tab and next/previous tab buttons is clicked, it focuses on the heading of the tab's content.
- Read styles from XHTML item._text and apply it to children items.
- Fixed infinite updating of string-based calculatedExpressions when the input is empty and the new value is Falsy (null, undefined, "", etc)
- Display items now do not classify as HTML labels.
- Only allow valueCodings to have system, code and display properties. This is to prevent unexpected properties in the QuestionnaireResponse causing validation errors.
- Restore flex-grow: 1 in ItemLabel and GroupHeading to work with XHTML and markdown renderings with 100% width
(WARNING: Major breaking changes with MUI, theming and rendererStylingStore)
- Allow overriding of Typography "groupHeading" to dictate stylings of group headings
- Allow overriding of Typography "label" to dictate stylings of item labels (replacing
itemLabelFontWeightin RendererStylingStore) - Add (a much-needed) JSDoc for RendererStylingStore.
- Group headings now have a proper sequence for heading semantics based on level of nesting i.e h1, h2, h3, h4, h5, h6
- Upgraded to Material-UI v6. Follow the migration guide to update your MUI to v6.
- Changed
tabListFixedWidthto a more flexibletabListWidthOrResponsive. - Changed
itemLabelGridBreakpointsanditemFieldGridBreakpointsto a more flexibleitemResponsive. itemLabelGridBreakpointsis nowitemResponsive.labelBreakpoints.itemFieldGridBreakpointsis nowitemResponsive.fieldBreakpoints- Allow customisation of gaps between item labels and fields via
itemResponsive.columnGapPixelsanditemResponsive.rowGapPixels. - Refactor
ItemLabelandGroupHeading.ItemLabelWrapperis now calledItemLabel. - Refactor
typographyOptionsin renderer theme to have increased font sizes. - Remove custom backgrounds, shadows and colours from theme.
- Minor font size adjustments throughout components.
- Changed flyover icon and text.
- Removed
itemLabelFontWeightfrom RendererStylingStore. Use MUI Typographylabelto customise item label styling.
- Fixed sequencing of
groupCardElevation.
(WARNING: Breaking changes for id-based e2e testing)
- Associated labels in ItemLabelText explicitly (via htmlFor + id) to all item types except time.
- All input ids are now prepended with item.type i.e. item.type + "-" + item.linkId
- Add support for required-based validation and the useValidationFeedback hook to all item types except date and dateTime.
- Add feedbackFromParent property in QItemOverrideComponentProps and SingleItem to manually pass feedback into a single item.
- Implemented highlightRequiredItems function in QuestionnaireResponseStore to manually highlight required items in the UI.
- Add useValidationFeedback support to boolean and radio buttons.
- Add support for "required-feedback" extension (custom extension) to customise displayed feedback for required items.
- Remove false positive FHIRPath warnings due to unresolvable x-fhir-query variables.
- Added support for the targetConstraint extension for target constraint-based validation and item feedback.
- Fixed an issue where higher fixed width values for the tab list may cause the tab content to wrap below the tab list.
- Added a hook to set a fixed width for the tab list within a tabbed form in RendererStylingStore.
- Fixed an issue where the default tabbed form breakpoint is set to render at a width lower than "md" rather than higher.
(WARNING: This version will break the renderer, use 1.0.0-alpha.20 instead.)
- Added a hook to adjust breakpoints for rendering a tabbed form in RendererStylingStore.
- Increased renderer's tolerance when working with valueCoding without codes.
- Fixed an issue where unexpected properties in valueCodings from a terminology server e.g. designation would not be filtered from the QuestionnaireResponse and cause validation failure when submitted to a FHIR server.
- Updated dependencies to fix incompatible Node and dependency versions.
- Added preferredTerminologyServer compatibility with valueUri.
- Changed how the .env file controls how Vite handles preserveSymLinks to play nice with CommonJS modules. It is worth re-reading LOCAL_DEVELOPMENT.md for local development setup.
- Added hook to hide tab button in RendererStylingStore.
- Added checks for "0" values in maxQuantity and minQuantity validation.
- Added terminology caching in FHIRPath's memberOf() to significantly improve performance for async FHIRPath evaluation.
- Updated fhirpath.js to v3.17.0.
- Added support for maxQuantity and minQuantity SDC extensions.
- Added a local development guide.
- Fixed build issues with v1.0.0-alpha.10.
- Removed unintended (i) icon at the end of a markdown display item.
(WARNING: Breaking changes from v1.0.0-alpha.9)
- Updated fhirpath.js to v3.15.2, which uses async functions for FHIRPath evaluation. A large number of functions have been updated to use async/await syntax.
- Updated sdc-populate to v3.0.0, which is also updated to use async functions for FHIRPath evaluation and updated FetchTerminologyCallback API.
Note: this version doesn't build properly, use v1.0.0-alpha.11 instead.
- Added support to hide optional Quantity comparator field.
- Changed Quantity's unitOption behaviour to not show the unit dropdown if there is only one option.
- Exposed more functions in the library API. No logic changes were made.
- Added support for custom validation feedback via custom extensions e.g. https://smartforms.csiro.au/ig/StructureDefinition/minValue-feedback
- Added support for inputs to use flex-grow to fill available space instead of a fixed numeric width.
- EnableWhenAsReadOnly now allows specifying an array of itemTypes to be rendered as read-only fields. Unspecified itemTypes will use the default behaviour of hiding the item.
- Added support in RendererStylingStore to adjust required indicator position (start/end), boolean yes/no position, text field width and show/hide clear button for item fields.
- Fixed group item "required" validation.
- Added support in RendererStylingStore for customising item label and item field breakpoints for responsive design.
- Added support for Boolean checkboxes via the 'check-box' itemControl.
- No changes were made in this release. This version was published to fix a versioning issue.
- Added RendererStylingStore config for enableWhenAsReadOnly. This allows the renderer to display enableWhen items as read-only fields instead of hiding them if enableWhen conditions are not met.
- Added SDC UI itemControl (https://hl7.org/fhir/extensions/ValueSet-questionnaire-item-control.html) overrides in buildForm() to substitute the default look with a React component via
code. Only works for flyover components ATM.
- Modified page rendering behaviour to align with the examples in the SDC specification.
- Added support in RendererStylingStore to disable/enable card view and "next page" button configs for
Page.
- Added RendererStylingStore to provide customised rendering/behaviour for the renderer via library API.
- Added QuestionnaireItem overrides in buildForm() to substitute a specified QuestionnaireItem with a React component via linkId.