Alex Marcat

Turns out ` (response.headers as any).lazyInit(); ` was needed at the start of the ResponseInterceptor. Which kinda makes sense, being a lazy initializer, but I wonder why in the default...

> I've made a discovery of a workaround. Setting `qt.force_software_rendering` to `chromium` has vastly improved the lag issue. Lag still happens, but it's almost always usable now, feeling like stuttering...

Maybe the help is not specific enough, but since I implemented that part, I can answer: Since statcode handles both status codes as well as headers, the all options wouldnt...

This seems to happen on gentoo too (: `error: could not compile `exa` Caused by: process didn't exit successfully: `rustc --crate-name exa --edition=2018 src/main.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C...

Any workaround that you know of to solve this issue? It's really frustrating I can't seem to be able to handle this

Maybe I am just dumb, but why cant perseResponse be moved after the plain return?

This is still happening. This is a lot worse, for instance, if you have a resource which actually has some field left undefined in the server, then you change it...

Also, to clarify: that happens even if you add the field anywhere else in your application code, not just the interceptor

Also if I changed the value somewhere (i.e. in an ngModel 2-way binding), the plain will return the old value actually