Replies: 1 comment 2 replies
-
|
That's all good, just deal with it on a new PR, dedicated to making Hatch work. This way other work can continue in parallel. I made the same mistake with my PRs, they need to be:
My PR was about changing the script behavior, but I bundled it with my automatic test script. |
Beta Was this translation helpful? Give feedback.
-
|
I'm not sure how to continue in parallel, at this point. I promised not to submit any changes until there's test coverage to prove them. But all unit testing remains blocked on #240. In case anyone still thinks this is more complicated than it is, I hope you'll find DEVELOPER.md reassuring. 🙏
|
Beta Was this translation helpful? Give feedback.
-
|
At this point the existing tests complete, so we're just waiting for JipHop to come back from vacation - no? |
Beta Was this translation helpful? Give feedback.
-
Oh, no no no! 😱 Hatch was pivotal to keeping things simple for code quality tools in a project with multiple authors.
What Hatch does for us is cleanly wrangle all of the other tools for unit tests, regression tests, code coverage reports, static analysis, and style consistency. Immeasurable value; discreet footprint.
None of us wants to deal with all of those separate tools and their interactions on our own, or to have them litter up the repo. VSCode does some of that same work for you privately, but helping others run preflight checks and having ongoing reporting happen in CI is invaluable to soliciting other contributions while maintaining a coherent codebase. Please reconsider.
Beta Was this translation helpful? Give feedback.
All reactions