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
We should expose react-router to query writers so they can build pages and links:
# redirect to another route in a functiona=ui.dashboard(
returntable.on_row_press(lamdadata: ui.redirect("/my-other-dash/data['sym']")
)
# hooks for url location and paramsb=ui.dashboard(
[sym] =ui.use_params([null])
returnt=table.where(f"{sym}"
)
# works like react router link, doing SPA navigationhome=ui.dashboard(
returnui.link("My Dash", href="/my-dash")
# declare a router with paths and the component the path loadsrouter=ui.router({
"/": home,
"/my-dash" : a,
"/my-other-dash/:sym" : b,
})
On enterprise we could include the pq name as part of the path /app/{pq-name}/my-dash, implicitly if the link is for the current PQ, and explicitly for linking to other PQs.
ui.link("My Dash", href="/my-dash") # implicitly the current pqui.link("My Other PQ Dash", href="/app/my-other-pq/my-dash")
The text was updated successfully, but these errors were encountered:
What if multiple scripts register the same routes? Does a user “open” the router object or does it automatically register?
How are the implicit vs. explicit links differentiated?
We should expose react-router to query writers so they can build pages and links:
On enterprise we could include the pq name as part of the path
/app/{pq-name}/my-dash
, implicitly if the link is for the current PQ, and explicitly for linking to other PQs.The text was updated successfully, but these errors were encountered: