Are you struggling to enforce custom code conventions in large codebases? Learn how to automate this process while maintaining a consistent CI time using Pylint and Pants Build. Attendees will be able to apply the stack in their own codebases right away.
Have you ever been discouraged while trying to enforce code conventions in large codebases?
While growing good and long-lasting projects means getting more features, more contributors, and more sub-projects, as a company or community, experience tells one they need rules and code conventions.
It gets particularly true with mono-repositories and large frameworks. Enforcing these rules becomes more and more complex and time-consuming as the code base gets larger and the community grows. We will illustrate how to automate such rules enforcement and ease the contributors' life.
It turns out Pylint brings the ability to have custom linter rules, and Pants Build helps us manage multi-project repositories, let's merge these two worlds and build an industry-grade project.
This talk aims to illustrate the power of this setup and how it can help developers work with large repositories while enforcing specific and strict rules.
Takeaways for attendees, that can be put into action right away:
* Be able to apply stricter rules to their code while it grows
* Keep a constant CI time while scaling, even with more linting rules
* Keep tools isolated, portable and safe
Base code, config, and extra documentation will be available for attendees to build their setup.
