[Long Callback] Support pattern matching for long callbacks side updates (progress/cancel/running)

[T4rk1n]

Long callbacks progress, running and cancel dependencies should support pattern matching ids.

[milind]

Was this issue ever resolved? I think that I'm running into it in my current application in trying to assign a pattern-matching component to the cancel parameter.

[Ciaran-YouSeq]

thank you @T4rk1n - can I ask if there are plans to add pattern matching for progress, running and cancel in the near future?

[T4rk1n]

@Ciaran-YouSeq It's in the backlog... If anyone want to work on this it would be a good introduction to renderer development, I can give some pointers below.

The side update are performed in this function:

dash/dash/dash-renderer/src/actions/callbacks.ts

Lines 322 to 336 in 093b559

	function sideUpdate(outputs: any, dispatch: any, paths: any) {
	toPairs(outputs).forEach(([id, value]) => {
	const [componentId, propName] = id.split('.');
	const componentPath = paths.strs[componentId];
	dispatch(
	updateProps({
	props: {[propName]: value},
	itempath: componentPath
	})
	);
	dispatch(
	notifyObservers({id: componentId, props: {[propName]: value}})
	);
	});
	}

We have a function to get path from id:

dash/dash/dash-renderer/src/actions/paths.js

Line 70 in 093b559

export function getPath(paths, id) {

The side update will need to be integrated with the getPath function, the returned path in that case may be a array of path or a path itself, then modify the dispatch to be on a loop depending on that result.