-
Notifications
You must be signed in to change notification settings - Fork 18
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
url_search parsing a shinylive app #28
Comments
shouldn't
be
|
yes, for the specific problem posed. So it probably would have been better to have the example include that. Admittedly, I got distracted while constructing the example and saw that |
@thebioengineer no worries was just mentioning in case that was the issue. I'm equally curious about parsing query parameters. Glad you asked the question. |
Oooooooo! I think I got this one haha. The issue comes from the app being run in an iframe. The query string / hash are not being forwarded. Smaller app that shows all information in the JS console: library(shiny)
ui <- fluidPage(verbatimTextOutput("search_values"))
server <- function(input, output, session) {
observe({
str(reactiveValuesToList(session$clientData))
})
output$search_values <- renderText({
invalidateLater(1000)
paste(capture.output({
print(Sys.time())
str(getQueryString())
}), collapse = "\n")
})
}
shinyApp(ui, server) While at url
If I updated the iframe's
🎉 Will make a PR in shinylive |
Amazing! Many thanks for looking into this.. hopefully it was an interesting one. |
George beat me by two weeks 🤣 We will wait on posit-dev/shinylive#79 . |
So I imagine I should be able to pass this by just running either of the below?
|
I have an app from my screencast that I tried to turn into a shinylive app that takes advantage of session$clientData$url_search to pull in the query params from a user. Once I used shinylive to convert it, the queries passed to the URL did get passed onto the shinylive shiny session.
Not sure how large of use-case this is, but I would imagine some folks might want bookmarking to function so flagging for your attention.
The text was updated successfully, but these errors were encountered: