gewenyu99

6 ms·

1. 1.▲
   by gewenyu99 2y ago

   A journal reaching top of Hackernews? What is this?
2. 2.▲
   by gewenyu99 2y ago

   What's the point here over like just hitting rerun and maybe just hitting rerun again? I mean I feel like you shouldn't have a bunch of flaky tests anyway if you're writing them properly
3. 3.▲
   Cleaning up the code base: how to avoid missteps(mindful-coding.com)

   1 points by gewenyu99 2y ago|0 comments
4. 4.▲
   by gewenyu99 2y ago

   Yes, we sponsored them because we have a commercial product that uses ESLint and we want to contribute back to open source. I don't see why this is an issue. We also wanted to show them our metalinter, which we believe has genuine use
5. 5.▲
   ESLint adopts Trunk as new linter runner in their repo(trunk.io)

   2 points by gewenyu99 2y ago|2 comments
6. 6.▲
   by gewenyu99 2y ago

   Us, from Trunk.io: "Oh look we're at the top of Hackernews! Oh wait it's not us"
7. 7.▲
   by gewenyu99 2y ago

   Looks better these days than beginning of year ngl
8. 8.▲
   by gewenyu99 2y ago

   Well, we built Trunk Check to address some of these issues. Maybe it'll suit your org better. - We support hold-the-line: we only lint on diffs so you can refactor as you go. Gradual adoption. - Use existing configs: use standard OSS t