search

bodil / eslint-config-cleanjs

An eslint config which reduces JS to a pure functional language
1.1k stars 33 forks source link

Idea: Enforce 100% covering by Flow #11

Open steida opened 8 years ago

steida commented 8 years ago

Atom somehow shows how much code is covered by Flow. CleanScript demands 100% I guess.

steida commented 8 years ago

This is it https://github.com/gajus/eslint-plugin-flowtype

yantakus commented 7 years ago

@steida what do you mean by "this is it"? I can't see any rules in eslint-plugin-flowtype to enforce 100% flow coverage.

steida commented 7 years ago

@yantakus I mean, we can add such rule.

yantakus commented 7 years ago

Yes, would be great.

r01010010 commented 7 years ago

I totally second this.

devinrhode2 commented 7 years ago

I also think Flow would be an amazing compliment to this project. I found this repo through my interest in elm, and think that for somebody initially interested in elm, that person would usually give preference to flow instead of typescript, because flow shares the goal of no runtime exceptions with elm. (These are some pretty good slides, and this one in particular really hit home for me: https://djcordhose.github.io/flow-vs-typescript/2016_hhjs.html#/21)

Flow gives you more type safety per type signature: https://medium.com/the-thinkmill/adopting-flow-typescript-3549a3a36d51

And you don't have potential tooling conflicts because of the different file extension.

On 01/06/2017 8:23 AM, "Paloma Jiménez" notifications@github.com wrote:

I totally second this.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/bodil/eslint-config-cleanjs/issues/11#issuecomment-305491576, or mute the thread https://github.com/notifications/unsubscribe-auth/AAg8qLG5L9k1YAvZE7NGIZ6icsHYqdQ-ks5r_rs7gaJpZM4J4i38 .