FlowMake performs typecheck for whole project #36

Activity

1. michaelowens commented on Oct 4, 2016

   

   michaelowens

   on Oct 4, 2016

   More actions

   Same is happening for me, both on save and FlowMake it will show errors for the whole project, not the current file.
2. mvolkmann commented on Dec 18, 2016

   

   mvolkmann

   on Dec 18, 2016

   More actions

   I think there really needs to be an option to only check the current file.
3. mvolkmann commented on Dec 18, 2016

   

   mvolkmann

   on Dec 18, 2016

   Last edited by mvolkmann

   More actions

   I've been looking into this. I think there's a bug in the flow#typecheck function.
   This line:

   let flow_result = <SID>FlowClientCall('--timeout '.g:flow#timeout.' --retry-if-init false'.expand('%:p'), '2> /dev/null')
   

   needs a space after --retry-if-init false.

   However, I think the bigger issue is that this needs to use check-content in order to check just one file. I tried changing that line to this:

   let flow_result = <SID>FlowClientCall('check-contents < '.expand('%:p').' --timeout '.g:flow#timeout.' --retry-if-init false', '2> /dev/null')
   

   That generates only errors for the current file, but it apparently doesn't generate the desired output for populating the quickfix window.

   I verified that "flow check-content" doesn't generate the same kind of error output as plain "flow". Pretty sure this is the issue with my attempted solution above. Not sure what I can do about that.
4. mvolkmann commented on Dec 27, 2016

   

   mvolkmann

   on Dec 27, 2016

   More actions

   Can we get some feedback from committers as to whether this is something that should be fixed? If it's desired to fix this, but nobody has time right now, I might be willing to submit a pull request.
5. ckjoris commented on Dec 28, 2016

   

   ckjoris

   on Dec 28, 2016

   More actions

   im not a committer, just want to let you know that theres a flow linter for https://github.com/w0rp/ale vim plugin, and it shows warnings for only current buffer.

   👍React with 👍1Reacted by Riley Tomasek
6. mvolkmann commented on Dec 31, 2016

   

   mvolkmann

   on Dec 31, 2016

   More actions

   Wow, this was wonderful advice! It took me awhile to get it configured, but I'm loving ALE! I have switched from Syntastic to ALE. Here's a screenshot showing Flow in action. I customized the error and warning signs to be emojis.
   
7. codeaholicguy commented on Jul 6, 2017

   

   codeaholicguy

   on Jul 6, 2017

   More actions

   I have the same question, is there any option to check the current buffer only?
8. zfogg commented on Apr 18, 2020

   

   zfogg

   on Apr 18, 2020

   More actions

   +1 to this