Side effects (ie network requests)

[keeslinp]

I mentioned this briefly in the rustlang thread but maybe that conversation would be better continued here.

I'm playing around with this library and I'm a huge fan so far. I'm interested in contributing and so I started making a simple example site to see where the unimplemented parts are of this library so that I could help out. I noticed that there was no paradigm set up for side-effects or asynchronous code, such as network requests. I was able to perform async code and mutate the model using Rc<RefCell<>> but it would not call the view again until another update triggered a re-render.

Elm handles this scenario using Commands. Is this the same way that you want to solve this problem in yew? Or is there another solution that seems more "rusty"?

[therustmonk]

Hi! Thank you for the issue! I've merged last changes (#11) where I've implemented Services concept. It works like subscriptions in Elm, but more flexible and handy. In the next few days I will implement Fetch for you. I already have a prototype implementation ;)

Timeout service example: https://github.com/DenisKolodin/yew/blob/master/examples/timer/src/main.rs
How to implement a service: https://github.com/DenisKolodin/yew/blob/master/src/services.rs

[keeslinp]

Awesome! I'll definitely play around with that. Thanks :). I have an open PR adding network requests to stdweb so if that goes through you could base your fetch request on that (it seems that you are already using stdweb). koute/stdweb#50

[keeslinp]

I was able to get it working by writing a custom network service that used by branch of stdweb. Once I can get that merged in I'll put up the site that I used as an example. For now I'll close this issue because the problem is resolved.