Mention flow init when doesn't find .flowconfig #19
Comments
skratchdot
added a commit
to skratchdot/flow
that referenced
this issue
Nov 18, 2014
fixes facebook#19. I'm not sure what the policy is on multiline error messages, but this looked a little better on separate lines IMO. I tested the change locally. I'm also not sure if this extra message is needed once people become familiar with the tool (or look at the --help options). I found out pretty quickly I needed to run `flow init`, so I'm guessing others will as well. Feel free to ignore/close this pull request. I figured it was a ticket I could close out quickly (when looking at the issues).
skratchdot
added a commit
to skratchdot/flow
that referenced
this issue
Nov 18, 2014
fixes facebook#19. I'm not sure what the policy is on multiline error messages, but this looked a little better on separate lines IMO. I tested the change locally. I'm also not sure if this extra message is needed once people become familiar with the tool (or look at the --help options). I found out pretty quickly I needed to run `flow init`, so I'm guessing others will as well. Feel free to ignore/close this pull request. I figured it was a ticket I could close out quickly (when looking at the issues).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This would be nice to make this error message more explicit as to what you need to do to fix
"I don't have any idea why flow makes an error message 'Could not find a .flowconfig in . or any of its parent directories'"
The text was updated successfully, but these errors were encountered: