walter

[walter @BrbWalter]

@housecor The record should have a “version” field which bumps on every update.
This field is mandatory on API side (in input), so if a gateway receive an old version then it could return 409 conflict to the client

[walter @BrbWalter]

@puruvjdev @builderio @e18e_dev

[walter @BrbWalter]

@TkDodo Useful but not needed.
Signature:
setData: ((data: TData) => void) | ((updateFn: (prevData: TData) => TData) => void)

If create an element on a list in this way a user does not need to read from cache, update and then write to cache

[walter @BrbWalter]

@drosenwasser Changing branch; or build linked packages

[walter @BrbWalter]

@mattpocockuk Missing assertion matcher for refinements / missing narrowing for example on tagged unions:
expect(foo.tag).toBe(‘myTag’) | expect(bar).toBe(E.right(expect.anything()))

[walter @BrbWalter]

@DavidKPiano Accept all incoming changes 😁

[walter @BrbWalter]

@erikras Simply: equals(x, y)
https://t.co/ZKVb9AHPDo

[walter @BrbWalter]

@v8js The switch statement is using the catched `err` (which is probably an instance of Error) , but for the case statements you are using strings. How is it possibile? 😅

[walter @BrbWalter]

@ryanflorence The issue is the signature of Array.prototype.find . If you use a function `find<A>(arr: A[], predicate: (a: A) => boolean): undefined | A` typescript will help you a lot more on spotting this kind of bug

[Ray [REDACTED] @RayRedacted]

Rage Against the Machine Learning

[walter @BrbWalter]

@mjackson Implementation for `unsafeCoerce`:
return a as any

[walter @BrbWalter]

@mjackson You can use this function: `declare function unsafeCoerce<A, B>(a: A): B`
Where A is the "problematic" type you have, and B Is the correct type you want.
With this function you can work with type safety After the coercion (instead of working with `any`)

[walter @BrbWalter]

@vincentriemer translateX/Y should be more performant than top/left properties because it happens in the composite stage (end of the pipeline) and not in the layout stage, which can cause page reflow.
See: https://t.co/UQ6Nkbyk7G

[walter @BrbWalter]

@n0ther_guy @dan_abramov Does the reader evaluate faster the meaning of the common case because of conventions / algorithm flow? 😁

[walter @BrbWalter]

#ngwin awyeah!

[walter @BrbWalter]

@_ericelliott If confident with this notation` * SECONDS` can be also replaced with `e3`:
console.log(1e3);
console.log(30e3);

[walter @BrbWalter]

I just downloaded The Data Playbook 📖 by @auth0. Learn how to put your data to work! 📈 https://t.co/T6rlNyNYlw

[walter @BrbWalter]

I just downloaded The JWT Handbook 📖 by @auth0. Everything you wanted to know about JWTs in one place. Check it out! https://t.co/ik7tKphsbF

[walter @BrbWalter]

@JedWatson how do you handle :before and :after for styling purpose?