If you update the nested component's (i.e., the Child instance's) query params, and then try to get the query of the parent component, the parent's query does not reflect the new child query params.
The rendered path used in re-indexing won't reduce a unique ident to its corresponding dispatch key. See here
The indexer uses the rendered path as a lookup key in :data-path->components. See here
Meanwhile, :data-path->components index is updated using keys that are data-paths where the path reduces keys that are a ident to dispatch key. See here, here, here, and here.
The solution is to use dispatch keys instead of unique idents when calculating the rendered path during re-indexing.
Consider the following example:
If you update the nested component's (i.e., the
Child
instance's) query params, and then try to get the query of the parent component, the parent's query does not reflect the new child query params.i.e.,
I tracked the reason why this fails:
:data-path->components
. See here:data-path->components
index is updated using keys that are data-paths where the path reduces keys that are a ident to dispatch key. See here, here, here, and here.The solution is to use dispatch keys instead of unique idents when calculating the rendered path during re-indexing.
Will submit a PR.