I have set some custom shortcuts in a module and they work when I'm viewing that module. However, when I put that module into an app, the custom shortcuts no longer seem to work.
Is this a bug or expected behavior? Can't find anything about the intersection of custom shortcuts and modules in the documentation.
Is there a way to set custom shortcuts in an app that reference components/queries in a module? When I try to add custom shortcuts to an app that contains a module, the components/queries of the module don't autocomplete in the custom shortcuts action text field for me.
Happy to help here! I believe this functionality is not currently supported but definitely understand how this UI can be confusing. I'll make sure to fill out a bug report and keep this thread open as a fix is addressed, thanks for flagging!
Thanks, Chris. For me, ideally the custom shortcuts set in a module could be inherited wherever the module is included and in the case of conflicting custom shortcuts in the parent, the parent's shortcut would take precedence.
Hey @jeffbowen — definitely agree, this would make the most sense. I've gone ahead and filed a bug report here and will keep this thread up to date as I hear back on this from my team! :)
Essentially, you can use a variable in the parent app as an input to the module whose value is the timestamp of the last time the hotkey combination was pressed. In the module, use a JSON SQL query to watch the input with a success handler that runs the script you'd like to fire on success. Any time the timestamp changes, the script runs.