v5.1.0

Core 5.1.0 contains various critical fixes for issues stemming from the 5.0.0 BREAKING release. In addition, it contains a number of new features and improvements.

Highlights

Support for feature flags

This release introduces a new feature flagging system to O3. Feature toggles (often referred to as feature flags) are powerful, allowing teams to modify system behaviour without changing code. This is useful for features still in development or features not yet ready for production use. Implementers will be able to toggle features on and off from the Feature Flags tab in the O3 Implementer Tools. See @brandones' GIF below demoing feature flags in practice:

Initial support for RDE

v5.1.0 introduces initial support for Retrospective Data Entry. It contains changes to the visit-utils file and the useVisit hook to allow the user to manually set the current visit. Prior to this, the concept of the current visit only referred to the latest visit with no end date. This change sets the stage for proper RDE support in the future.

Post-migration fixes

This release provides several fixes for issues related to the 5.0.0 release, including fixes to the configuration, extension, and translation systems. With these, we should be able to confidently move forward with the 5.x series of releases.

Features

• (feat) Load scripts for non-visible modules asynchronously after starting the application by @ibacher in #710
• (feat) KH-239: Translate login page to km by @kdaud in #716
• (feat) Improved {locale}.json translation files for various languages by @vasharma05 in #705
• (feat) More flexible system for setting the current visit (supports O3-1895) by @brandones in #724
• (feat) Simplify the openmrsComponentDecorator by @ibacher in #725
• (feat) O3-2258: Create feature flagging system by @brandones in #728
• (feat) O3-2258: Extension system support for feature flags by @brandones in #733

Bug fixes

• (fix) Various fixes for compatibility of new versions by @ibacher in #707
• (fix) Extensions should have meaningful names by @ibacher in #708
• (fix) Restore proper extension order by @ibacher in #709
• (fix) Fix loading config from relative URLs by @ibacher in #703
• (fix) Add a missing order property to the offline tools routes by @denniskigen in #711
• (fix) Fix routes for offline tools frontend module by @denniskigen in #712
• (fix) Fix offline tools dashboard link by @denniskigen in #713
• (fix) Properly merge routes using routes.registry.json from backend by @ibacher in #714
• (fix) Improve service-worker behaviour when running in development by @ibacher in #715
• (fix) Render extensions based on connectivity by @denniskigen in #717
• (fix) Fix issues with single-spa caused by naming extensions by @ibacher in #720
• (fix) Define behaviour for translations from esm-app-shell by @ibacher in #719
• (fix) Attempt to ensure we only have one i18next instance by @ibacher in #721
• (fix) Importmap replacement should only override importmap.json part of importmap URL by @ibacher in #722
• (fix) Login app should load locations with a case-insensitive db by @ibacher in #723
• (fix) Ignore single-spa error 32 firing if a parcel has been unmounted by @ibacher in #729
• (fix) Update a bunch of peer dependencies from 4.x to 5.x by @brandones in #730
• (fix) Restore suspense wrapper to openmrsComponentDecorator by @ibacher in #731
• (fix) Remove side scrolling in the Location picker in tablet and small desktop by @Jexsie in #701
• (fix) O3-2258 trivial fixup: Add useFeatureFlag to esm-react-utils public exports by @brandones in #734

New contributors

• @kdaud made their first contribution in #716

Thank you to all our wonderful contributors! 🎉

Full Changelog: v5.0.2...v5.1.0