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
Flow has this .js.flow file pattern. If utilized correctly, a consumer won't have to change anything in their .flowconfig in order to get the flow typings for mobx.
We'd have to remove the wrapping module block from the .js.flow file and add export to all declared variables that are exported. I've already done this locally to test it, so I could immediately open a PR.
Projects using MobX with flow typings would have to remove the [libs] line from their config when they upgrade.
The text was updated successfully, but these errors were encountered:
The PR has been merged, however if I understand it correctly it does not solve the issue described above? (Properly exposing the types). Would you be interested in submitting a PR for that as well?
Flow has this
.js.flow
file pattern. If utilized correctly, a consumer won't have to change anything in their.flowconfig
in order to get the flow typings formobx
.We'd have to remove the wrapping
module
block from the.js.flow
file and addexport
to all declared variables that are exported. I've already done this locally to test it, so I could immediately open a PR.Projects using MobX with flow typings would have to remove the
[libs]
line from their config when they upgrade.The text was updated successfully, but these errors were encountered: