David Pedersen
David Pedersen
Currently `LiveView::{mount, update}` allows you to return an error. If that happens the view is shutdown and the client will reconnect and a new view is created. However I'm not...
While `update` is being called no other events will be processed and insert put into a queue. So if you do slow async stuff (like making web requests) your view...
There are a few `console.error` and `unimplemented!` in the client and server side code. I haven't been able to hit those in tests. Should look into that so we don't...
The client side code is getting sufficiently complicated that we need to add tests for it. I'm thinking mainly the `ViewState` patching.
So users can style things different for example if the connection is broken.
All public items must have docs and we should add a bunch more examples. This is blocked on building more parts of the API. I don't feel we should spend...
CSRF tokens
[Phoenix uses CSRF tokens](https://hexdocs.pm/phoenix_live_view/Phoenix.LiveView.html), we might need to as well but I don't know a whole lot about CSRF tokens so not sure how to implement them. https://en.wikipedia.org/wiki/Cross-site_request_forgery
Phoenix liveview supports file uploads, with progress bars. I don't have experience with it but we should consider something similar for this.
### Expected behavior In normal library/binary crates `Neomake` works just fine, but in [Cargo workspaces](https://doc.rust-lang.org/book/second-edition/ch14-03-cargo-workspaces.html) it does not. Nothing happens when running `:Neomake`. ### Steps to reproduce I have made...