If this is a bug, please try reproducing using https://flow.org/try/.
No
@TrySound Is that mean flow already had better tooling ?
It's improved with every release. Do you know flow has lsp (language server protocol) support which is universal for a bunch of editors? Error messages a few releases ago became realy nice. Linters do a great job on making your code stricter.
Just watch commits. They are like a blog.
@TrySound I love to adopt to flow and we are using it our project. but now it is like using nothing. because of windows issues. At some point we are unable to enforce static typing. It would be great if this tooling is improved. I’m not sure of very recent releases. But some issues like this till exist
https://github.com/facebook/flow/issues/6424
Yeah, there was some problems when I was on windows. But all I have to do is to rerun flow a few times per day. I used neovim with ale. It worked stable enough for me. I think most issues are related to bad IDE integrations, mostly webstorm.
But if you could view pull requests like #6424 developers are crying for help. In my case it it restarting frequently. It is turning unreliable. Can these issues be taken as priority so every one can use flow as it advertised ? or There is a pull request that I have created to update the documentation to help developers to start thinking about the problems that they have to deal with. https://github.com/facebook/flow/pull/5659
Closing because:
But with that in mind, I'd be happy to help review a full re-write. Feel free to submit a PR and tag me in it ¯\_(ツ)_/¯
@sagar12861 I'm sorry it's not working properly for you-- flow is far form perfect but that' doesn't mean flow is not being worked on, as you can see by the commit history. Unfortunately, a limited number of people work on it and not all bugs can be worked on with the same priority.
Most helpful comment
No