Nick SzaunigandClaude Sonnet 5
b208f52fd1
None of these numeric business fields had a lower bound, so a negative honey weight, jar count, feeding amount, mite count, or stock quantity was silently accepted - each would corrupt whatever total or statistic it later feeds into. Added @Min(0): - Harvest: honeySuperCount, grossWeight, netWeight - HoneyBatch: amount (+ @Max(100) on waterContent, a percentage) - HoneyMeasurement: waterContent (+ @Max(100)) - Feeding: amount - Extraction: amount (+ @Max(100) on waterContent) - StockItem: quantity, minThreshold - VarroaMeasurement: durationMinutes, miteCount, calculatedValue Left temperature fields alone (extraction, inspection) - genuinely can be negative (winter inspections, outdoor storage) and no confident domain bound exists to apply instead. Update DTOs for these entities all extend PartialType(PickType(Create...Dto, [...])) from @nestjs/swagger, which preserves validation decorators, so no separate change was needed there. Co-Authored-By: Claude Sonnet 5 <[email protected]>
49 lines
787 B
TypeScript
49 lines
787 B
TypeScript
import { ApiProperty, ApiPropertyOptional } from '@nestjs/swagger';
|
|
import {
|
|
IsDateString,
|
|
IsEnum,
|
|
IsNumber,
|
|
IsOptional,
|
|
IsString,
|
|
Min,
|
|
} from 'class-validator';
|
|
import { FeedType } from '../../../generated/prisma';
|
|
|
|
export class CreateFeedingDto {
|
|
@ApiProperty()
|
|
@IsString()
|
|
colonyId!: string;
|
|
|
|
@ApiProperty()
|
|
@IsDateString()
|
|
date!: string;
|
|
|
|
@ApiProperty({ enum: FeedType })
|
|
@IsEnum(FeedType)
|
|
feedType!: FeedType;
|
|
|
|
@ApiPropertyOptional()
|
|
@IsOptional()
|
|
@IsString()
|
|
product?: string;
|
|
|
|
@ApiProperty()
|
|
@IsNumber()
|
|
@Min(0)
|
|
amount!: number;
|
|
|
|
@ApiProperty()
|
|
@IsString()
|
|
unit!: string;
|
|
|
|
@ApiPropertyOptional()
|
|
@IsOptional()
|
|
@IsString()
|
|
batchNumber?: string;
|
|
|
|
@ApiPropertyOptional()
|
|
@IsOptional()
|
|
@IsString()
|
|
notes?: string;
|
|
}
|