bridgeUiPathResolversIntoRegistry
bridgeUiPathResolversIntoRegistry(
resolvers,registry?): () =>void
Bridge an SDK-init uiPathResolvers map into a CtaResolverRegistry
so resolvers supplied at init actually dispatch on CTA clicks (plan 174
TASK-1 / F-70). Called by the SDK constructor after the init-time coverage
check runs.
Explicit registrations take precedence: an action type already present in
the registry (via registerCtaResolver or a direct register) is
left untouched, and a later explicit registration replaces the bridged
entry through the registry’s normal override semantics. Each bridged
resolver receives the placement’s raw authored cta_path record — the same
shape init-time validation checked. A rejected async resolver is logged,
never thrown into the click handler.
Returns a cleanup function that unregisters exactly the entries this call bridged, skipping any the customer has since replaced.
Parameters
Section titled “Parameters”resolvers
Section titled “resolvers”Record<string, (uiPath) => void | Promise<void>>
registry?
Section titled “registry?”CtaResolverRegistry = ...
Returns
Section titled “Returns”() => void