Add OpenAPI tests for using various attribute data types #1832
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds OpenAPI tests for using various data types in attributes that behave like values, such as
Int128/BigInteger/Half/Uri/IPAddress/Versionand various others.Depending on the built-in support (which varies per technology), the following custom converters may need to be added:
FilterParserand overrideGetConstantValueConverterForTypeChanges in this PR:
RuntimeTypeConverter.GetFriendlyTypeName(), which expands generic type argumentsRuntimeTypeConverterSystem.UriinRuntimeTypeConverterLiteralConstantExpression.GetStringValuefor date/time valuesSumFilterParserexampleDespite mentioned in the original issue, tuples are not covered because exposing them in an HTTP API is just odd.
Complex types and collections are not covered either, because how they work is likely going to change when #1439 is implemented.
Closes #1051.
QUALITY CHECKLIST