Alexey Makhrov
Alexey Makhrov
@jmroon they covered the subject in the blog post: https://blog.angular.io/how-the-angular-compiler-works-42111f9d2549 My understanding is that the TS errors that TS compiler produces for those TCBs are surfaced directly to the user...
this is basically a blocker for using it with our OAS 2.0 spec
Nope, the demo looks as if nothing changed: > - Only the "start" thumb is rendered in SSR > - The the start thumb is rendered in the left-most position...
Is it possible to define all positions relatively in percents instead of absolutely in px? This way, we wouldn't need `getBoundingClientRect()`
It affects us, too. We don't even want to share artifacts. Just regular `yarn install` before running Cypress would benefit from yarn cache - which is always missed due to...
@brjadams we didn't move on with it, and just turned off inline critical CSS in the meantime
> I think if the below is valid then the fix would be apart of this issue, so posting here: > > In `@angular/router/router.d.ts`: > > ``` > /** >...
Makes sense. Probably also can be resolved by having a looser (any) type for programmatic navigation input, but stricter type when consuming it from the route (ActivatedRoute.queryParams)
This also happens to me without using `get` directly - when I call `patchState` serially a few times (inside a complicated observable pipe, which, I assume, executes queueScheduler somewhere). Looks...
I ended up updating our existing templates that used `ngSwitch` to using `ngIf` - the latter properly supports type narrowing.