Generator system

[thetutlage]

The generator system will be used to create types for various things. It includes

• Scanning Inertia pages and creating a types file for them. This action should run anytime a file is changed inside the inertia/pages directory.
• Creating types for registered routes. This action should run every time the HTTP server is restarted (so we can use the start method from the providers)
• Creating the frontend routes client for creating URLs. This action should run every time the HTTP server is restarted.
• Creating an index file with lazy imported controllers. It will cleanup the imports inside the routes file. This action should run anytime files are changed inside the controllers directory with the ability to specify a custom source for controllers.
• Creating types for HTTP transformers. This action should run anytime a file is changed inside the app/transformers directory.

Updates

• Added RoutesScanner
• Added IndexGenerator and integrate it with the DevServer and the TestRunner

Related commits and PRs

• adonisjs/assembler@194861c
• https://github.com/adonisjs/assembler/releases/tag/v8.0.0-next.6

[iamtommcc]

Just a quick question with all this ongoing codegen work/E2E type safety/delightful grep-ast magic going on recently... will scanning directory patterns always be configurable?

For my larger apps I find using a domain module approach (e.g. app/publications/controllers, app/publications/transformers) helps a lot for reasoning around large codebases. I know in modern day Laravel land this approach is becoming increasingly popular.

[thetutlage]

Yes, it will be configurable. This is how you can tell the scanners to look for controllers in a DDD setup.

hooks: {
  init: [
    indexEntities({
      controllers: {
        enabled: true,
        source: './app',
        glob: '**/controllers/**/*.ts',
      }
    })
  ]
}