Claude
297d3bfe77
BREAKING CHANGE: cereale moves from legacy `experimentalDecorators` to TC39
standard decorators, which is what makes validation rules type-checked against
the fields they are attached to.
class User {
@IsString() name!: string; // fine
@IsString() age!: number; // Type 'number' is not assignable to 'string'
}
Legacy decorators receive (target: any, key: string) and lose the field type
entirely, so this was impossible in v1. Standard decorators receive
ClassFieldDecoratorContext<This, Value>, which carries it. Rules now checked:
scalar rules against scalar fields; { each: true } against arrays, in both
directions; @JsonType against the field's class; @JsonSerialize/@JsonDeserialize
against the field's type; @IsIn and @IsEnum against the field's value type.
17 tests invoke the real compiler to assert the wrong code stays rejected — a
guarantee nobody checks is one that quietly stops holding.
Positioning follows the capability: validated domain objects, not validated
data. The README now leads with the Zod comparison. Cereale does not infer your
type from a schema — you still write the field type and the rule — but it
guarantees the two cannot disagree, which is what class-validator never offered.
Removed
- metadata-storage.ts and its WeakMap singleton. Metadata lives on
context.metadata now, which also removes the dual ESM/CJS double-singleton
hazard. Inheritance merging becomes structural rather than reconstructed on
every read, so the subclass-shadowing defect fixed by hand in 0.1.0 cannot
reoccur by construction.
- registerDecorator, replaced by defineRule(Class, 'field', constraint).
Unchanged: the engine, options, naming strategies, access control, error
helpers, the sync API, and the performance work. 193 tests pass.
Toolchain note: standard decorators are transformed by tsc and esbuild, but not
yet by oxc. The library builds with tsc and consumers on esbuild/Vite are fine;
Vitest 4 uses oxc, so the test runner needs an esbuild transform plugin. This is
recorded in vitest.config.ts and the README, and is the reason 1.x should stay
available for oxc-based toolchains.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SAcqrz3FcadkYr3xG32CjK
45 lines
1.3 KiB
JSON
45 lines
1.3 KiB
JSON
{
|
|
// Visit https://aka.ms/tsconfig to read more about this file
|
|
"compilerOptions": {
|
|
// File Layout
|
|
"rootDir": "src",
|
|
"outDir": "dist",
|
|
|
|
// Environment Settings
|
|
"module": "NodeNext",
|
|
"target": "ES2025",
|
|
"lib": ["ESNext", "ESNext.Decorators"],
|
|
"types": ["node"],
|
|
|
|
// Other Outputs
|
|
"sourceMap": true,
|
|
"declaration": true,
|
|
"declarationMap": true,
|
|
|
|
// Stricter Typechecking Options
|
|
"noUncheckedIndexedAccess": true,
|
|
"exactOptionalPropertyTypes": true,
|
|
|
|
// Style Options
|
|
"noImplicitReturns": true,
|
|
"noImplicitOverride": true,
|
|
"noUnusedLocals": true,
|
|
"noUnusedParameters": true,
|
|
"noFallthroughCasesInSwitch": true,
|
|
|
|
// Recommended Options
|
|
"strict": true,
|
|
"strictPropertyInitialization": false,
|
|
"isolatedModules": true,
|
|
"skipLibCheck": true,
|
|
|
|
// NOTE: no `experimentalDecorators`. v2 uses TC39 standard decorators, which is what
|
|
// gives ClassFieldDecoratorContext<This, Value> and therefore compile-time checking of
|
|
// rules against field types. The two decorator systems cannot coexist in one program.
|
|
},
|
|
// NOTE: test files are deliberately included here so that `npm run type-check`
|
|
// covers them. The two build configs exclude them (and the demo) from `dist`.
|
|
"include": ["src/**/*"],
|
|
"exclude": ["node_modules", "dist"]
|
|
}
|