[Question]: Specify max and min range for double and decimal datatype

[c6-dark]

What are you wanting to achieve?

Because of some requirements, I want to specify max and min values of decimal and double datatype for both of them but in the above case, the swagger is not showing maximum and minimum for both.

What code or approach do you have so far?

[Range[decimal.minvalue, decimal.maxvalue)]
public decimal amt { get; set; }

[Range[double.minvalue, double.maxvalue)]
public double pamt { get; set; }

How do I achieve the above so the max and min value of decimal and double is shown in swagger

Additional context

No response

[amabilee]

Hey there!
Have you tried the Swashbuckle.AspNetCore.Annotations package?

[c6-dark]

Hey, I am using that package. It doesnt support decimal.maxvalue or decimal.minvalue, or double.maxvalue, double.minvalue

[martincostello]

This is the code that handles [Range]:

Swashbuckle.AspNetCore/src/Swashbuckle.AspNetCore.SwaggerGen/SchemaGenerator/OpenApiSchemaExtensions.cs

Lines 190 to 213 in fc77e5a

	private static void ApplyRangeAttribute(OpenApiSchema schema, RangeAttribute rangeAttribute)
	{
	#if NET8_0_OR_GREATER
	if (rangeAttribute.MinimumIsExclusive)
	{
	schema.ExclusiveMinimum = true;
	}
	if (rangeAttribute.MaximumIsExclusive)
	{
	schema.ExclusiveMaximum = true;
	}
	#endif
	schema.Maximum = decimal.TryParse(rangeAttribute.Maximum.ToString(), out decimal maximum)
	? maximum
	: schema.Maximum;
	schema.Minimum = decimal.TryParse(rangeAttribute.Minimum.ToString(), out decimal minimum)
	? minimum
	: schema.Minimum;
	}

On inspection, it looks like it would support decimal and double.

If it's not working maybe it's a bug? Please provide a minimal reproducible example as a GitHub repository that demonstrates the issue you're experiencing so we can look into this further.

[github-actions]

This issue is stale because it has been open for 60 days with no activity. It will be automatically closed in 14 days if no further updates are made.

[github-actions]

This issue was closed because it has been inactive for 14 days since being marked as stale.