* feat(fullstack): add `render_handler_with_state`
When using server functions, the current pattern to access state such as
database connections is to use `register_server_fns_with_handler` on an
Axum router and 'inject' the state into the context provided to the
server function. However, this only affects function calls which go via
the Axum router; SSR renders bypass this, and therefore don't have
access to any state.
This commit adds an alternative `render_handler` which accepts some
additional state. That state is injected into the context in a
similar manner to `register_server_fns_with_handler`. SSR renders can
then proceed to run in the same way as HTTP calls.
* Change state object to 'inject_state' callback
Also add a compiling doctest example.
* remove the explicit for<'a> lifetime
* remove unused assets_path from render_handler_with_context example
---------
Co-authored-by: Evan Almloff <evanalmloff@gmail.com>
* fix false notification/rebuild for dx hot-reload
* Make sure we have permissions and the changed file exists before reading the metadata
---------
Co-authored-by: ealmloff <evanalmloff@gmail.com>
* Related to #1547: use `dioxus-cli` within a workspace
Although the `dx` CLI allows to specify a package name to chose from workspace members,
it does not support workspace members specified as glob-wildcards.
Neither it respects the effective package name, specified in the crate's `Cargo.toml`.
This PR addresses that issue:
- upon `dx build ...`, if the `--bin` CLI-argument is provided, treat the current dir as a workspace;
- search through the workspace's `members`: resolve each of them with `glob`;
- assume that any workspace member has a `Cargo.toml` in it (cargo does it, so it's okay);
- read said manifest, and check the package name in it;
- if found — there we have our sought package.
* Use cargo-metadata to find out the workspace structure
* glob is unused
* Fix GoForwardButton calling can_go_back instead of can_go_forward
* Add first draft of LiveviewHistory
* Add external URL redirect
* Lock evaluator channel outside loop
* Add liveview to router examples
* fixup! Add liveview to router examples
* Communicate with liveview server on page load
* Add PopState event to Liveview routing
* Call updater callback from liveview history
* Add rudimentary PopState functionality to liveview router.
* Fix linter errors
* Refactor
* Fix navigator external redirection not working.
* Add go back and go forward buttons to router examples
* Finish functionality for timeline stack in liveview router
* Add docs to LiveviewHistory
* Replace Liveview history context attachment with constructor that takes context
* Fix go forward/backward history/future shuffle
* Support history across entire liveview session, if contiguous page jumps.
* Remove unnecessary bounds
* Add query and hash to location string
* Run rustfmt
* fix: Update server function docs link (#1489)
* liveview: Add `interpreter_glue_relative_uri (#1481)
* liveview: Add `interpreter_glue_relative_uri`
By utilizing `window.location.host` in the client-side JavaScript, we can easily derive the WebSocket URI from a relative path URI. This approach obviates the need for host address retrieval on the server side, unlike the method of serving glue code in liveview using `interpreter_glue`.
* liveview: Merge `.._relative_url` functionality
- Merged `.._relative_url` to current API `interpreter_glue`.
- Edit axum example to work with new feature.
* liveview: Fix clippy warning
* Rename modules to use snake_case (#1498)
* Change Scope into &ScopeState
* Move synchronization of state into router and make it opt-in
---------
Co-authored-by: Marc Espín <mespinsanz@gmail.com>
Co-authored-by: Seungwoo Kang <ki6080@gmail.com>
Co-authored-by: Leonard <tigerros.gh@gmail.com>
Co-authored-by: Evan Almloff <evanalmloff@gmail.com>
