Nick SzaunigandClaude Opus 5
42ceb33844
Both records could be created but never changed. A water-content reading decides whether a batch may be sold as honey at all, and queen ratings drive breeding decisions - a slipped digit in either is exactly the kind of wrong value that must not be left standing. - New PATCH /honey-batches/measurements/:measurementId behind honey-batches:measure, and PATCH /queens/evaluations/:evaluationId behind queens:evaluate. Both are addressed by the child record's own id, so the routes take two path segments and do not collide with PATCH /:id. - Both log before and after data, like every other correction. - The measurement list on the honey batch page and the rating list on the queen page gained an edit dialog; the rating dialog reuses the existing criteria list rather than restating it. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
11 lines
366 B
TypeScript
11 lines
366 B
TypeScript
import { PartialType } from '@nestjs/swagger';
|
|
import { CreateQueenEvaluationDto } from './create-queen-evaluation.dto';
|
|
|
|
/**
|
|
* Breeding decisions are made from these scores, so a rating entered against
|
|
* the wrong queen or with a slipped digit has to be correctable.
|
|
*/
|
|
export class UpdateQueenEvaluationDto extends PartialType(
|
|
CreateQueenEvaluationDto,
|
|
) {}
|