The command gen-flow-files has been around a while now, and it's been almost untouched since it was released as an experimental command in v0.32.0 about a year and a half ago. I'm unaware of any libraries using this in production (probably because for most use-cases it just doesn't work).
I think there are dangers of leaving such a buggy/experimental command in there with no active intent on fixing/updating it:
- Library maintainers could be waiting indefinitely for an update rather than seeking out alternative means (like flow typed or flow-copy-source)
- Library maintainers might be publishing buggy lib-defs without realising it.
- Or worse, they can be frustrated by
gen-flow-files so much that they abandon Flow types altogether.
I think the command should be deprecated and ultimately removed, and documentation updated to reflect the official recommended pathway to publishing types, whatever that may be.
The command
gen-flow-fileshas been around a while now, and it's been almost untouched since it was released as an experimental command in v0.32.0 about a year and a half ago. I'm unaware of any libraries using this in production (probably because for most use-cases it just doesn't work).I think there are dangers of leaving such a buggy/experimental command in there with no active intent on fixing/updating it:
gen-flow-filesso much that they abandon Flow types altogether.I think the command should be deprecated and ultimately removed, and documentation updated to reflect the official recommended pathway to publishing types, whatever that may be.