Josh Pike
Josh Pike
If 'Animal but not Dog' doesn't make sense, that is something TS can be aware of and disallow. But including something like ButNot into TS syntax I think is a...
If `Dog = Animal & { woof:string }` then `Animal && !Dog` would be equivalent to `Animal & !(Animal & { woof:string })`, which would always evaluate to false. But...
I just don't want defaults at all. We have jest but it's a dependency of another library that only runs in CI and needs several arguments. I'd rather this default...
@GeorgeKnap @johnpapa any plans for this?
it appears to not happen all the time. beyond that I have no more info to add
Any news? It's been 3 weeks now
We are still getting this error... is there any news on this?
It's now been two months. Things are getting ridiculous now, considering the premium rate we pay for this product.
@iainbreen can we have an update on this? It's been SIX MONTHS since I opened this ticket. We pay a solid sum to Intercom. All I expect is a working...
closing cause I don't care anymore, i'll just ignore the error and move on. incredible.