Table of contents
Unfortunately, the best solution, according to this blog post, is, surprise, surprise, to subscribe to their product (which also encourages devs to embrace brain-dead practices like empty commit messages and squash-merges, which gives me little faith in their product, but I digress). So I guess those of us who can't or won't cough up a subscription fee are just hosed. Source: over 1 year ago
I would say any styleguide that is in prose form and not machine enforced is deficient. Modern linting and formatting tools are the best, most efficeiect means for enforcing style. No religious arguments are needed if the tooling decides what is correct. Shameless plug for https://trunk.io/products/check - which will handle universal enforcement of all the tooling for all of the pieces of your tech stack. - Source: Hacker News / almost 2 years ago
I actually recently joined a startup working on this problem! One of our products is a universal linter, which wraps the standard open-source tools available for the different toolchains, simplifies the setup/installation process for all of them, and a bunch of other usability things (suppressing existing issues so that you can introduce new linters with minimal pain, CI integration, and more): you can read more... - Source: Hacker News / over 2 years ago
Do you know an article comparing Trunk.io Check to other products?
Suggest a link to a post with product alternatives.
This is an informative page about Trunk.io Check. You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.
