Maybe someone with more expertise can chime in here, but I think Yew is written in a way that assumes that there will always be a post-mount lifecycle to each element, i.e. to handle prop changes or state updates, which wouldn't necessarily need to be true in SSR, so there might be some relaxation of the necessity to implement VDiff that could be achieved through a refactor.
@philip-peterson yeah I think we might want to disable VDiff for SSR. Not sure what that would look like right now though
@jstarry Thanks for the advice. I'll try to implement all of them because I'm actually just trying Yew out right now. Agents are quite cool but It feels like I'll have to implement everything twice.
@JonasZ95 awesome, be sure to report back your findings on that issue. It hasn't been too active lately
The RouteAgent::Bridge(callback) is throwing an error,
error[E0599]: no function or associated item named `bridge` found for type `yew_router::agent::RouteAgent<_>` in the current scope
|
74 | let router = RouteAgent::bridge(link.callback(|_| Message::Ignore));
| ^^^^^^ function or associated item not found in `yew_router::agent::RouteAgent<_>`
|
= note: the method `bridge` exists but the following trait bounds were not satisfied:
`&mut yew_router::agent::RouteAgent<_> : yew::agent::Bridged`
`&yew_router::agent::RouteAgent<_> : yew::agent::Bridged`
`yew_router::agent::RouteAgent<_> : yew::agent::Bridged`
= help: items from traits can only be used if the trait is in scope
= note: the following trait is implemented but not in scope; perhaps add a `use` for it:
`use yew::agent::Bridged;`use yew::agent::Bridge;
use yew_router::agent::RouteAgent;
pub struct Model {
router: Box<dyn Bridge<RouteAgent>>
}
let router = RouteAgent::bridge(link.callback(|_| Message::Ignore));
wasm-pack build seems to run ok, but when i try to run rollup i get this https://pastebin.com/zfPVY6ku . again to stress I am new to rust/yew/wasm/webdev/arguably programming in general :P so fairly blindly doing stuff without any inherent understanding, so apologies in advance if it's something painfully obvious
VComp::generate_ssr you mean a new variant of vcomp.rs#l15?
@adante_twitter I had to remove a few things to get your project to build.
First, remove your main.rs file. It isn't required for a wasm-pack built projects because wasm-pack builds your application as a library (lib). It's not a binary so there's no main entrypoint.
Second, remove the fn main() function in your lib.rs
I was able to build and run your project after that with these commands:
wasm-pack build --target web
rollup ./main.js --format iife --file ./pkg/bundle.js
python3 -m http.server 8080How can I cause a user to be prompted with a file download dialog in response to user interaction? When a user performs some action, such as clicking a button, the app will calculate the URL of a file and somehow cause the download dialog to appear for the user
@kellytk afaict you have to use <a> tags to download files https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a
use yew::agent::Bridged;?
Index => html! { <div> { format!("Rendering for route {:?}", switch)} </div> }, When I navigate to /login this is rendering Rendering for route Login but within the Index handler!
html! macro, because slimming down that gets rid of the error
html! macro so perhaps it is in the error reporting process?
let on_login = self.on_login.clone();
html! {
<Router<AppRoute> render = Router::render(|switch: AppRoute| { match switch {
AppRoute::Login => html! { <login_form::LoginForm on_login=on_login /> },on_login inside render captures the definition outside, so the render closure is an FnOnce, not an Fn
stdweb or web-sys depending on which you are using