Is your feature request related to a problem? Please describe.
The current generation of the *ValidationAttributesMap objects generated the type as:
export const BauprogrammCreateDTOPropertyValidationAttributesMap: {
[property: string]: {
maxLength?: number,
minLength?: number,
pattern?: string,
maximum?: number,
exclusiveMaximum?: boolean,
minimum?: number,
exclusiveMinimum?: boolean,
multipleOf?: number,
maxItems?: number,
minItems?: number,
uniqueItems?: boolean
}
} = { ... }
This makes the TS compiler unaware of the actual keys existent in the object and thus disabled auto completion and type safety when working with the *ValidationAttributesMap objects.
Describe the solution you'd like
I suggest to define a generic ValidationAttributes interface containing the type and removing the explicit type declaration from generated ValidationAttributeMaps. satisfies check would then keep the type safety for the Map objects themself intact.
Since ValidationAttributes would be a type thats not related to a specific model, the type should be defined centrally only once. (e.g. in runtime?)
Describe alternatives you've considered
--
Additional context
--
Is your feature request related to a problem? Please describe.
The current generation of the
*ValidationAttributesMapobjects generated the type as:This makes the TS compiler unaware of the actual keys existent in the object and thus disabled auto completion and type safety when working with the
*ValidationAttributesMapobjects.Describe the solution you'd like
I suggest to define a generic
ValidationAttributesinterface containing the type and removing the explicit type declaration from generatedValidationAttributeMaps.satisfiescheck would then keep the type safety for the Map objects themself intact.Since
ValidationAttributeswould be a type thats not related to a specific model, the type should be defined centrally only once. (e.g. inruntime?)Describe alternatives you've considered
--
Additional context
--