You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 24, 2019. It is now read-only.
I was having issues with running my tests, because I didn't realise this is not acknowledging flowconfig file. In my flowconfig I have all=true, but to get flow-remove-types/register work in the same way, I have to pass {all: true} to the module.
The text was updated successfully, but these errors were encountered:
This would certainly be handy, but I don't see it happening soon - We probably don't want to duplicate Flow's .flowconfig lookup and parsing logic here. If at some point we split that code out of Flow in a form we can publish to npm (like we do for flow-parser) then this would become feasible.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I was having issues with running my tests, because I didn't realise this is not acknowledging flowconfig file. In my flowconfig I have all=true, but to get
flow-remove-types/register
work in the same way, I have to pass{all: true}
to the module.The text was updated successfully, but these errors were encountered: