-
Notifications
You must be signed in to change notification settings - Fork 52
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
Fix #40: SharedData across shiny modules #114
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixes #40 |
cpsievert
reviewed
Nov 9, 2021
tests/testthat/test-crosstalk.R
Outdated
expect_identical(shiny::isolate(sd1$selection()), res) | ||
expect_identical(shiny::isolate(sd2$selection()), res) | ||
|
||
sess$setInputs(".clientValue-foo-selection" = c("149", "150")) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggested change
sess$setInputs(".clientValue-foo-selection" = c("149", "150")) | |
sess$setInputs(".clientValue-foo-selection" = as.character(c(nrow(iris) - 1, nrow(iris)))) |
cpsievert
approved these changes
Nov 9, 2021
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please also add a news item, thanks!
SharedData group should transcend modules (it's a global namespace). This isn't as crazy as it sounds, because the default group value is a random ID. `SharedData$new(..., group = session$ns("groupname"))` can be used to opt into namespaces if that's desired. Note that this change doesn't break a scenario that works today; before this commit, the reactive accessors on SharedData that originated in modules, simply did not work.
jcheng5
force-pushed
the
joe/bugfix/modules
branch
from
November 10, 2021 03:29
0584937
to
28c5d15
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The bug:
SharedData
objects constructed inside Shiny modules, were not returning any values forsd$selection()
and other reactive methods. This is because the id sent to the client and the id used by the server weren't the same--the server version had the module's namespace automatically prefixed. With this fix, the server uses the same id as the client.Implementation notes
SharedData group should transcend modules (it's a global
namespace). This isn't as crazy as it sounds, because
the default group value is a random ID.
SharedData$new(..., group = session$ns("groupname"))
canbe used to opt into namespaces if that's desired.
Note that this change doesn't break a scenario that works
today; before this commit, the reactive accessors on
SharedData that originated in modules, simply did not work.
Testing notes
Run the following app. Select some points on the plot. Without the fix, the reported number of selected points is 0; with the fix, a correct number is reported. (Note that it might sometimes seem like the reported number is a little too high--this is because of overplotted points, and is almost certainly actually the correct number.)