New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Name space issue with Shiny modules using pre-generated java script links #1261
Comments
|
I'm not able to follow the example. Could you provide a simplified version that strips it down to just the necessary components? |
|
Yeah, that example is a bit crazy. When I first ran into the problem, that was the app scenario. But, I now know there are others like the one show in this example. I answered my own question after getting it to work with 'global' NS function: It seems like you need the NS function to be global to write shiny module code that works on UI / server side. I found it to be hacky at first. But, I am not sure there is any better solution. |
|
Closing because the original issue was resolved by using the |
I am trying to use shiny modules to re-use the UI and server code to present off of three different data sets that share the same presentation.
Running into a bit of a challenge dealing with namespace when using javascript based modal popup link creation outside of the UI / server code.
Here is my non-working app code:
A working version would successfully display
myLinkNamein the description portion of the modal pop up. The reason this code does not work is because the UI component ID value is created outside of the UI code without the namespace containment. I get that. But, I am not able to figure out how to re-work it so that the name space matches.I don't want to generate the table and links dynamically, if avoidable as the table size is large.
Any ideas / options?
UPDATE:
Using a namespace definition 'outside' and then using paste to string together the java script line seems to work. But, this seems like a gigantic hack.
Is this the best that can be done?
The text was updated successfully, but these errors were encountered: