A NEST.js route conflict checker
Luter interpret the nestjs controller file passed in as path argument and extracts all routes inserting them in trie data structure for evaluation
if a route contains a ":param" followed by another param in the same route it becomes a conflict beacause other routes will be injected in as param for that endpoint bug founded in nestjs/swagger
- add the possibility to scan an entire nestjs project;
- refactor and optimization;
- auto correction of bad routes?;
- integration in nestjs codebase?;
- Make the executable
make- Launch the exe
./luter x.controller.tsP.S. I chose to use C not because I wanted to shoot myself in the foot but because I wanted to learn the language with a project in mind. 😂