Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
This can be achieved with a schema filter. For this proof of concept, I based the filter on a custom attribute: [AttributeUsage(AttributeTargets.Property)] public class GreaterThanAttribute(doubl...
Answer
#1: Initial revision
This can be achieved with a schema filter. For this proof of concept, I based the filter on a custom attribute: ```C# [AttributeUsage(AttributeTargets.Property)] public class GreaterThanAttribute(double exclusiveMinimum) : Attribute { public double ExclusiveMinimum { get; } = exclusiveMinimum; } ``` ```C# public class GreaterThanFilter : ISchemaFilter { public void Apply(OpenApiSchema schema, SchemaFilterContext context) { if (context.MemberInfo?.MemberType == MemberTypes.Property) { var attr = context.MemberInfo.GetCustomAttribute<GreaterThanAttribute>(); if (attr != null) { schema.ExclusiveMinimum = true; schema.Minimum = (decimal)attr.ExclusiveMinimum; } } } } ``` Add the schema filter to `SwaggerGenOptions`: ```C# services.AddSwaggerGen(options => options.SchemaFilter<GreaterThanFilter>()); ``` The attributes that Swashbuckle recognizes by default are also recognized by EF Core. For consistency, you could also look for your custom attribute in your EF context `OnModelCreating` and make corresponding changes to the EF model.