Trotyl Yu
Trotyl Yu
> it's not the case that you haven't injected it anywhere. @julianobrasil If it's not injected, then likely no one has reference to that class, and it will be dropped...
> So instead I guess it would be `Observable`? Can be simplified to `Observable`.
Relates to https://github.com/angular/angular/issues/17616
FYI, there're indeed asynchronous DI support in the very alpha: https://github.com/angular/angular/issues/1623 https://github.com/angular/angular/issues/2813 But have already been dropped for years.
> One of the things that makes Javascript a ubiquitous language is that there is a big ecosystem of packages and a very small language core. @tobmaster I'd say JavaScript...
> Most who aren't developing for embedded, that is. On embedded, you might not even have a console to print to, so it doesn't always make sense to have a...
> operationally, how many of you would actually enjoy maintaining web-projects with polymorphic-classes with subclassed-properties having the same names as [unobservable] private-fields? @kaizhu256 The real problem is, one would never...
`undefined` is also a normal global variable in JavaScript (some people may not even aware of that), and every access to `[[global]].undefined` is not accidental, but deliberate. From the thread...
It's **NOT** caused by Angular, but a [XHR spec defined behavior](https://fetch.spec.whatwg.org/#concept-response-status-message). It would still be `OK` even after removing the `|| 'OK'` code in Angular.
Confirmed, the spec change was made at https://github.com/whatwg/fetch/pull/600.