Considerations for event_register with shiny modules

[john-harrold]

I'm looking to include a plotly element in a shiny module and I want to react to it. The way I'm doing that is using the event_register function. The event register seems like a UI ID. Is there any kind of best practices when using plotly/event_register in a shiny module to prevent namespace issues? Like should I reference it using NS: NS("mod_id", "my_plot")?

[dmenne]

Have you found a solution for handling a click event in a module? I cannot get rid of

The 'plotly_click' event tied a source ID of 'experiment_plot' is not registered. 
In order to obtain this event data, please add `event_register(p, 'plotly_click')` 
to the plot (`p`) that you wish to obtain event data from.

[john-harrold]

This is how I'm creating the ui element for shingy:

   uiele = plotly::ggplotly(fobj[["ggplot"]], source=paste0(id, "-results_fig"), tooltip=c("text"))
   uiele = plotly::event_register(uiele, "plotly_click")

To react to the clicks I'm doing this:

    observe({
      clk = plotly::event_data("plotly_click", source=paste0(id, "-results_fig"), priority="event")
     do_something_with_click(clk)
      })

[dmenne]

Thanks, John, looks like this is the second step: I had assumed that warning and not working event was a problem of namespaces with modules, but then reproduced it in a vanilla shiny app. I will revisit your suggestion after that is solved.