Brad Zacher

I think there is value in having at least a tracking issue. As an example from last night. The TS4.0 beta has released with support for Short-Circuiting Assignment Operators. In...

> We can briefly introduce on README about the folder structure: e.g. what extensions and experimental are for. If I know what stage a proposal is in, then sure, I...

> I'd say you should always start at tc39/proposals as source of truth I didn't even know that page existed!!! (I doubt a lot of people do) Whenever I'm told...

What do you mean by "shorthand"? Do you mean `{foo}` vs `{foo as bar}`? If so you can tell that by comparing the `.imported` and the `.local` properties on the...

Defining a new node type represents a significant breaking change for us when compared to the base ESTree spec, which can cause us all manner of issues with existing ESLint...

what in the sam hill is that syntax?!? It looks like flow completely ignores the type that's provided there: ```js const [a: number, b: string, c: boolean] = ['a', true,...

Quoting response from someone on the flow team: > It's not intentional. You're correct that the annotation is ignored. We should at least fix the parser to error here, and...

> Because of this there is a "hole" in the AST for the implements keyword. This isn't a problem. An AST node's children needn't explicitly wrap and cover every keyword....

note that a workaround for now is to add the required column to the `alwaysFetch` property. This will cause JM to always add it correctly to the shape.

a workaround we've found for this is to define the unique key as a composite of itself: `uniqueKey: ['id', 'id'],` This will add the unique key to the query as...