Version 1.0.0

• General
• Component CustomJSCmps is obsolete
• setInput() is now awaitable
• waitValueChanged() / CmpUtils.waitCmpValueChanged() not required anymore

General

Starting with this version, the components of a configurator are requested in a "pull-based" manner which means that data will only be transferred when actually required.
Other common terms for this behavior could be "load on demand" or "lazy loading".

For the developer, there shouldn't be any noticeable changes because the system decides itself when new data has to be requested from the server.

This behavior will automatically be active when the component CustomJSCmps doesn't exist.

Component CustomJSCmps is obsolete

With this version the component CustomJSCmps isn't required anymore to retrieve components in code.
If you're upgrading an older project you can simply delete this component.

setInput() is now awaitable

Awaiting the setInput() now guarantees the following when it resolves:

• Setting the input was fully processed
• All related components which are requested afterwards will have the latest value
• When there was no change (e.g. setting the same value again) it will also properly resolve

waitValueChanged() / CmpUtils.waitCmpValueChanged() not required anymore

Preceeding functions for which this was neccessary (e.g. setInput or CfgrUtils.convertHtmlToPdf) are now properly awaitable themselves.
When those functions resolve, it's now guaranteed that related components will contain the updated value.