Would i be correct in saying that Wappler's Node.js runtime does not pass the action's execution blueprint (exec) to custom modules during the live execution phase?
i am trying to create an extension which can access the exec parameters of a custom enquiry (parameter free) and extract the raw SQL used in the query.
Is this possible or should i stop trying as it can't be done?
(already spent hours with AI, it cant solve this, only suggests unsuitable workarounds)
Could you give some more context with examples of what data you would like to access.
Thanks for looking at this.
This post is also links to my feature request relating to dynamic dropdowns for hjson files.
Basically i was playing around with ideas around extensions to do actions such as dynamically create/ delete views based on a server connect queries and an extension to create/remove table indexes.
So my overall needs, in an ideal world, are to have the ability to show connections within globals, available tables and table fields defined within hjson UI definition files.
As a workaround for a view creation extension, i have been testing the idea of using a custom query and rather than taking the output, using the query name and finding the sql entry within the meta data and using it, via knex, to create the view (i am awre there will be parameter issues to resolve)
It appears that the metadata is not available within the app process or namespace?
I can send my .js code if you want to see it.