Feature/ext validation/request validation #15
Assignees
Relism (Zakaria El Orche)
Clear assignees
Relism (Zakaria El Orche)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Relism/Flash5#15
Reference in New Issue
Block a user
Boots a real app on an OS-assigned port for a test class or a single test and hands back a client pointed at it: @RegisterExtension static FlashTest app = FlashTest.of(new BlogApp()) .mock(UserService.class, new InMemoryUserService()); app.get("/api/users").expectStatus(200).expectBodyContains("alice"); A field rather than an annotation, because annotation values are compile-time constants and so could never express a second server wired from the first — FlashTest.of(new BlogApp(auth.baseUri())). Startup is lazy, so reading baseUri() boots that server on the spot and declaration order does the wiring, with no dependence on JUnit's extension ordering. A static field boots once per class, a non-static field once per test; that is stock JUnit field semantics rather than an option to configure. Runs against a real loopback port instead of dispatching in-process. An in-process dispatcher would be a third copy of the routing/handler/exception sequence that Http1Connection and Http2StreamDispatcher already duplicate, kept in sync by hand, and it would let a test pass while the status line, content-length or HPACK encoding was broken. mock() installs overrides as the last extension, after everything the application and its extensions declare, so a fake always wins. Any object is accepted, so a hand-written fake and a Mockito mock are equally welcome and this module depends on no mocking library — only flash and junit-jupiter-api. Teardown cancels the client before stopping the server: HttpClient holds keep-alive sockets open and ServerLifecycle.stop() spins until the last one closes, so the default 15s drain would otherwise be paid on every test class. shutdownNow rather than close(), which blocks until every operation completes and would hang on a leaked WebSocket. Lives at the top level, not under flash-extensions/, which holds things you install() onto an app; this carries junit-jupiter-api at compile scope and nothing installable should. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>Standard jakarta.validation annotations, compiled once per type into a flat check table. No configuration: constraints come from the annotations already on your types, and ValidationException extends HttpException with status 422 so the default handler renders it without this extension registering anything. record CreateUser(@NotBlank @Size(max = 80) String name, @Email String email, @Min(18) int age) {} CreateUser dto = validation.body(req, CreateUser.class); Annotations only — Hibernate Validator's engine is deliberately absent. It resolves constraints reflectively per call and pulls ~2 MB plus EL, which is the per-request cost this module exists to avoid. jakarta.validation-api is ~90 KB of annotations. The passing path allocates nothing. Constraints resolve at first use into an opcode plus operands cached in a ClassValue, so there is no map lookup and no lock. Fields are read through MethodHandles adapted to an exact signature — (Object)Object for references, (Object)long for primitive integrals — so invokeExact neither boxes nor builds the argument array Field.get and Method.invoke allocate. Checks are a flat array walked by a tableswitch rather than a class hierarchy behind a virtual call. @Size reads a length the object already knows and @Email scans with indexOf, because Pattern.matcher allocates a matcher and two int arrays per call. Messages are pre-rendered at compile time. The violation list and the exception exist only once something fails. @Pattern is the marked exception: its regex compiles once but matcher() allocates per call. Constraints are read from declared fields, so records and plain classes take one code path — a constraint on a record component propagates to its backing field. Jakarta null semantics are exact: only @NotNull rejects null. flash-ext-openapi now mirrors the same annotations into the generated schema — minLength, maxLength, minItems, minimum, maximum, pattern, format: email and required — via an optional jakarta.validation dependency detected at boot. A type declares its rules once and both the validator and the published contract read them. An explicit @Schema still wins; the bridge only fills keys nobody set, and without the annotations on the classpath the bridge class is never loaded. flash-ext-jackson is optional too: validate(value) works without it, only body(req, type) needs a codec. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>