Skip to content

Tags: koop/flow

Tags

v0.93.0

Toggle v0.93.0's commit message
v0.93.0

Summary: New Release

Reviewed By: jbrown215, pakoito

Differential Revision: D14055925

fbshipit-source-id: 4a0eec7ac10192eceab598c87dd3926d3cb4b711

v0.92.1

Toggle v0.92.1's commit message
v0.92.1

Reviewed By: pakoito

Differential Revision: D13945487

fbshipit-source-id: 7c90d96f2922ad7680bdc01c5eb35be5e918d9dc

v0.92.0

Toggle v0.92.0's commit message
v0.92.0

Summary: New release for 0.92.0

Reviewed By: panagosg7

Differential Revision: D13896533

fbshipit-source-id: 5e6a760b9cc21d7fbb0bc4ce31abdbbbfeadae9b

v0.91.0

Toggle v0.91.0's commit message
v0.91.0

Reviewed By: nmote, dsainati1

Differential Revision: D13703471

fbshipit-source-id: 93ab956fd3936479aa2c0cbcea13c7caff8d8e96

v0.90.0

Toggle v0.90.0's commit message
Fix opaque_id and class_id comparison in Flow_js

Summary:
An opaque type (resp. class instance type) is identified by the line and column span of
it's name at the point of definition. Across rechecks we consider the name of an opaque
type to have remained invariant iff the line and column span remains the same (regardless
of any discrepancies to the offset) -- see `add_loc` in sigHash.ml. This diff copies this logic
to the part of the checker that compares two opaque types.

`loc1 = loc2` is not equivalent to `ALoc.equal loc1 loc2` due to `offset`.

This caused bogus recheck errors to appear whenever the contents of a the file of a
remote opaque type changed, but not the line and column of the opaque type definition.

Reviewed By: avikchaudhuri

Differential Revision: D13614013

fbshipit-source-id: 6a775df51ea4f85799d34fd6223ad83e51699678

v0.89.0

Toggle v0.89.0's commit message
v0.89.0

Reviewed By: jbrown215

Differential Revision: D13439215

fbshipit-source-id: 230a547144d1a1f1a03f56c4067e084a181380bf

v0.88.0

Toggle v0.88.0's commit message
v0.88.0

Reviewed By: dsainati1

Differential Revision: D13371572

fbshipit-source-id: 425c7a9c27045cc3ec8cd32c9f98b46f81c1c830

v0.87.0

Toggle v0.87.0's commit message
Update 0.87.0 changelog with React.lazy and React.memo

Reviewed By: gabelevi, pakoito

Differential Revision: D13217025

fbshipit-source-id: 3245bb7dcc8278d048b318f2685edda50c5c18c7

v0.86.0

Toggle v0.86.0's commit message
allow configuring path to node during runtests.sh

Summary:
the custom resolver tests are relying on node from the path, but it can be helpful to override the path.

this diff introduces a `FLOW_NODE_BINARY` environment variable which you can point at a custom node:

```
FLOW_NODE_BINARY=path/to/node ./runtests.sh path/to/flow
```

This is accomplished via a wrapper script, `scripts/tests_bin/node`, which calls `$FLOW_NODE_BINARY`. `runtests.sh` sets the var to `NODE_BINARY` if it's set, or `which node` if not. `scripts/tests_bin` is added to `PATH` when running the tests, so `node` in tests picks up the wrapper.

Reviewed By: gabelevi

Differential Revision: D12964367

fbshipit-source-id: ef98fb1f89c6a32f04ef36ebb315a604f01c5e9e

v0.85.0

Toggle v0.85.0's commit message
v0.85.0

Summary: (Note: this ignores all push blocking failures!)

Reviewed By: avikchaudhuri

Differential Revision: D12834069

fbshipit-source-id: 544bddcca3e5193f6e5c4a1e802884a4f25ad859