Replies: 1 comment 9 replies
-
Indeed +data is executed after routing — it's tied to a page.
Can you elaborate on that? What's the use case you're trying to achieve?
How would that help? |
Beta Was this translation helpful? Give feedback.
9 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
hii
i have a use case where i render different views depending on the entity from the server response in
+data
.currently, i implement this by having a single page and selecting a view in the React code, which is problematic because the bundler can't exclude unused resources depending on the view
unfortunately, i don't see a proper way to pass the data from the "routing page" to the content page on the server side, besides saving it in the global state.
i think it would be helpful if the
throw render()
had the ability to pass a pageContext, similar to the client-sidenavigate()
Beta Was this translation helpful? Give feedback.
All reactions