Add conversions for types that support popular string formats #318
Labels
enhancement
New feature or request
Milestone
Comments
Closed
mwadams
added a commit
that referenced
this issue
Aug 8, 2024
1. This allows us to eliminate the last of the T4 templates 2. This dogfoods our codegen - the specs that test the non-validation capabilities of the core types become tests for our generated code as well as the core types themselves. - Adding code generation for all of the "format" extensions using the existing IFormatHandler (renamed from IFormatProvider) - This also fixes #318 - Implemented custom span-based parsers for OffsetDateTime, LocalDate, OffsetTime so they become zero-allocation allowing implicit casts to those types. - Optimized non-span/string-based parsing of netstandard2.0 IPAddress (v4/v6) and UUID.
|
Fixed in #393 - please try the Preview packages on nuget. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If a schema supports one of the common string formats, then it would be useful to support conversions to the relevant concrete string format types (e.g.
JsonUriTemplate,JsonUuid).At the moment it will (of course) convert with an
As<T>()-type cast, but there is no intellisense/type hint that this is possible.The text was updated successfully, but these errors were encountered: