What principle is followed when packaging ASP.NET Core rendering code with Sitecore code in the same module?

The principle that applies when packaging ASP.NET Core rendering code with Sitecore code in the same module is the Common Closure Principle. This principle states that classes that change together should be packaged together, essentially meaning that if two pieces of code are likely to change in tandem due to related functionality or requirements, they should be housed in the same module.

In the context of combining ASP.NET Core rendering with Sitecore, this is relevant because both the rendering code and Sitecore components will often be updated and modified together as they are related to the same functionality in a web application. By keeping them in the same module, you reduce the risk of inconsistencies that can arise from having related code separated, making it easier to maintain and evolve the application.

This practice supports modularity, maintainability, and reduces the likelihood of introducing bugs during updates, as developers can see all related code in one place. Other principles listed, while relevant to modular design, do not specifically address the concept of packaging closely related components together in the same context as the Common Closure Principle does.