CodeVetter · Repo Unpack · Data flow
adonisjs/core
Application-root URLs and RC configuration feed lifecycle creation and lazy container bindings. Incoming HTTP traffic crosses from a Node server into the dependency-provided framework handler, while local validation adapters assemble request data for VineJS. CLI inputs become command state, generated entities, AST transformations, or assembler operations. Development routing data is written to disk and announced to the parent process; standalone codegen passes equivalent serialized routes in memory. Verification tokens separate public secrets from hashes intended for consumer-owned persistence.
- Ignitor passes appRoot, environment, and importer into Application, then publishes the instance through setApp before running tap callbacks.
- Encryption configuration flows from app.config.get('encryption') through configProvider.resolve into EncryptionManager; the default Encryption class binding calls manager.use().
- HTTP requests and responses enter server.handle through a bound Node HTTP handler; the framework server retains the Node server through setNodeServer.
- RequestValidator spreads request.all() first, then assigns params, headers, and cookies from their request APIs, making these reserved fields override same-named body properties.
- Validation options receive request-specific defaults only when caller overrides are missing; options.data replaces automatic request assembly before validate or tryValidate receives the data.
- Multipart schema values are checked for the isMultipartFile marker; configured limits fill missing file limits, file.validate runs, and file.errors are translated into VineJS reports.
- Controller CLI input becomes an entity through app.generators.createEntity; the selected stub calculates class/file names and exports its destination through app.httpControllersPath before stub generation writes it.
- Committed router state feeds router.generateTypes(2), which is written as ScannedRoutes plus RoutesList augmentation; development output also serializes router.toJSON and notifies the parent of routesFileLocation.
- Standalone codegen JSON-round-trips router.toJSON to discard closure handlers and unserializable properties, then returns that route shape to the assembler callback.
- Edge clientRoutes exports only named routes and selects domain, methods, pattern, tokens, and name; routesJSON turns this selected structure into JSON.
- VerificationToken.seed returns a Secret and SHA-256 hash; transient tokens add userId and expiration, computeValue encodes identifier and secret, and verify compares a recomputed hash without performing persistence itself.