bootgs-validationlisted

# Bootgs Validation ## Available files - **`references/decorators-and-pipes.md`** — full list of validation decorators and Parse pipes. Load it when you need to check whether a specific constraint exists or what a pipe coerces to; the pattern for using them is below. ## Model bootgs validates individual **parameters**, not whole DTO classes — there is no class-validator-style `@ValidateNested`/decorated-DTO pipeline. A validation decorator stacks on top of an extraction decorator (`@Query`, `@Param`, `@Body`) and runs against the already-extracted value before the handler body executes: ```ts @Get() findAll( @Query("page") @Min(1) page: number, @Query("limit") @Max(100) limit: number, ) { /* page and limit are guaranteed valid here */ } ``` Multiple validators stack freely on one parameter; each runs in decorator-application order. The available decorators — `@Min`, `@Max`, `@Email`, `@Pattern`, `@Size`, `@NotBlank`, `@NotEmpty`, `@AssertTrue`/`@AssertFalse`, `@Positive`/`@PositiveOrZero`, `@Negative`/`@NegativeOrZero` — are listed with their exact checks in `references/decorators-and-pipes.md`. ## Parse pipes (extraction-time coercion) GAS delivers every parameter as a string. Use a Parse pipe as the **second argument** to `@Param`/`@Query` to coerce it before your handler sees it — don't hand-parse `Number(value)` in the handler body: ```ts @Get("{id}") findOne(@Param("id", ParseNumberPipe) id: number) { /* id is a number, not "42" */ } ``` Six are available (