Module Input Query Not Behaving Consistently

[emozio]

When I use a query as an Input to my module, and I go into that (variable) query from the module, there are a couple of options like success handlers. In essence, I've passed down a dynamic query and now want to extend on that behavior in another context.

In my experience, however, these success handlers, for example, don't have any effect. I am trying to attach certain behavior to the success handler, but it fails to do so.

Now, before you suggest to add this success handler to the original query, keep in mind that I want to be able to perform an action using the context I'm currently in.

Also, I noticed that the cache option is not enabled in the case of a "nested query", but I would expect this to be enabled or at least explained why it's not.

I am trying to organize modules in order to save myself from repeating certain logic and maintaining a DRY setup as much as possible. I know you've adviced against nesting modules, but the alternative isn't much better.

[emozio]

Because I realize this is quite a Inception-like topic, I thought I should add a screenshot to illustrate:

I am referring to any handlers added to the query that is undetermined. While the query itself is undetermined, I think the event handlers should remain functional until a query is provided.

[Tess]

Hi @emozio,

Thanks for reaching out about this! Unfortunately, the event handlers not triggering is a bug that we're tracking I don't have an eta but I will follow up here if it gets picked up

I see that caching is disabled for module input queries (see gif to confirm that's what you're referring to). I will look into it! We only support query caching for certain query types (it's not supported for Javascript queries, for example), so I'm guessing it is disabled just in case it isn't applicable