Brecht Billiet’s Post

Here is one of my favourite slides of my new Largescale #Angular architectures course: By using a custom refactor-lib NX generator we really get a lot of benefits: The goal is to refactor an existing NX workspace lib to a new scope and/or type. We can choose if it needs a new scope, a new type or a new scope and new type. The generator will do the following for us: - It will update the scope and the type tags of the project - It will update the directory of the lib - It will update the name of the lib in a consistent way according to our architecture - It updates the typescript Path mapping for us correctly - It's way shorter than the regular nx move command - It enforces consistency across the codebase This custom generator is set up in a matter of minutes, and helps us bring consistency and productivity to another level. If you like to know more about this, check the first comment 🚀

Wrote a little something on #Angular component architecture. Enjoy these 15 tips!

When using Nx, generator commands can become quite lengthy. This can be problematic for several reasons: - Typing these long commands is painful: Manually entering long commands increases the chances of making mistakes. - Human error: The longer the command, the higher the likelihood of errors, which can lead to inconsistent project setups. - Consistency: Ensuring that all team members use the same parameters every time is challenging. - Nx changes the API sometimes: Keeping up with changes in the Nx API can be difficult and can lead to outdated commands. - We want to enforce an architecture: Having a standardized approach to generating projects helps maintain a consistent architecture across the codebase. To address these issues, consider how we can simplify our generator commands. For example, instead of using a long command We could create a custom devkit command to simplify it. By doing this, we ensure that all necessary parameters are included by default, reducing the risk of errors and maintaining consistency. This approach also makes it easier to enforce architectural standards and adapt to changes in the Nx API, as updates to the custom devkit can be managed centrally.