strigefleur
strigefleur
Isn't it your NumLock disabled? Personally I use NumLock for auto-run so you know it's what often happens.
Same happens for 1.8.6 - would love to have some attention on that fact, since we can't immediately migrate to pg6.
Gotcha, thanks. I'll comment back as soon as we try this version.
``` The LINQ expression 'DbSet() // ... rest .Where(m => m.SomeDate.Date >= value && m.SomeDate.Date
I did, NeinLinq is at 6.0.0, EFCore is at 6.0.5. Will try to provide one tomorrow.
@dario-piotrowicz the point is taken; but could you please share the right way to deal with such a non-animatable properties that have to be set in the end of transition?...
I'm afraid I still don't get the idea to avoid the warning; using the simplified example: ```ts const collapse = trigger('collapseAnimation', [ state('expanded', style({ height: AUTO_STYLE })), state('hidden', style({ height:...
Thank you for the idea. Though I guess animation callback is way too much: imagine you have one prepared animation and tens of components using it - you'd have to...
Looking good, thanks :) I believe it still takes some efforts to solve the primary case we mentioned earlier (as to have some special way to define non-animatable styles within...
It should make use of [workers-timers](https://www.npmjs.com/package/worker-timers) to rely on instead of default timeout functions. Default timeout functions easily suspend on browser inactive tabs throttling.