You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm wondering if there is a possibility that a feature could be added whereby whereami::whereami() could have an argument to move up a level. Below I'll explain what I mean and why I think this would be useful.
I'm currently using whereami::cat_where(whereami::whereami()) many dozens of times throughout my Shiny app. I would like to be able to use the different types and colours but as it stands I'd need to do that in each instance. I would therefore like to create a wrapper function around this called something like log_reactivity(). But if I do this, every whereami() call would then just print that it is being called from log_reactivity(), which is not helpful. It would therefore be great if I could pop up a level (for some reason I'm imagining the function stack upside down, apologies if this isn't clear).
The text was updated successfully, but these errors were encountered:
Thanks for the package - it's really useful.
I'm wondering if there is a possibility that a feature could be added whereby
whereami::whereami()
could have an argument to move up a level. Below I'll explain what I mean and why I think this would be useful.I'm currently using
whereami::cat_where(whereami::whereami())
many dozens of times throughout my Shiny app. I would like to be able to use the different types and colours but as it stands I'd need to do that in each instance. I would therefore like to create a wrapper function around this called something likelog_reactivity()
. But if I do this, everywhereami()
call would then just print that it is being called fromlog_reactivity()
, which is not helpful. It would therefore be great if I could pop up a level (for some reason I'm imagining the function stack upside down, apologies if this isn't clear).The text was updated successfully, but these errors were encountered: