Skip to content

exclusiveMinimum and maximum does not make sense with ValueWithUnit object, it...

fabian serin requested to merge fserin/BUG_exclusiveMinimum_exclusiveMaximum_openapi into master

exclusiveMinimum and maximum does not make sense with ValueWithUnit object, it would make sense with float for instance. Removing this constraint does not remove the check with is done by a pydantic validator few lines below. It also fixes the open api generation which is now correct (this MR includes the reactivation of the fix)

Merge request reports