Hello,
While working on refactoring the configuration interfaces for our modules, I've taken a close look at the new configuration pages introduced in Ignition 8.3 and their implementation in React.
I noticed that some components — very useful for building configuration pages — are actively used internally (as seen in the 8.3 bundles), but are not publicly exposed via the @inductiveautomation/ignition-web-ui package. In particular:
ResourceModeSingletonPagePasswordInput- (and other similar building blocks)
These components clearly exist in the 8.3 source and are used in official pages like GatewaySettingsPage, yet they aren’t currently available to third-party module developers via public exports.
My questions are:
- Are these components planned to be exposed in the near future?
- Is there an intention to open them up as part of a public API (via
@inductiveautomation/ignition-web-uior another package)? Maybe expose@inductiveautomation/ignition-gateway-lib? - Is it recommended to rebuild these components ourselves at this stage?
- Or would it be better to wait for an official exposure?
- Is the
ignition-web-uilibrary mature enough today to justify migrating our custom configuration pages to it?
I’d like to:
- Avoid duplicating or rewriting components that already exist and work well,
- Stay aligned with the UX/UI patterns used by Ignition 8.3 for a consistent user experience,
- Preserve long-term maintainability (avoiding divergence, unnecessary wrappers, or technical debt).
Any visibility into the roadmap for SDK/UI components would be greatly appreciated in order to make an informed decision about migrating our modules.
