You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -396,9 +396,9 @@ There are three different property wrappers for `WrapConvertibleEnum` conforming
396
396
397
397
### <aname="dates"></a>Date properties
398
398
399
-
`WrapPropertyDate` (`WPDate`) handles several different formats of dates specified via an enum. Incoming translation from string attempts to decode from the specified date type first, but then also tries all the other types it knows about. Conversion back to string always uses the specified date type.
399
+
`WrapPropertyDate` (`WPDate`) handles several common formats of dates specified via an enum. Incoming translation from string attempts to decode from the specified date type first, but then also tries all the other types it knows about. Conversion back to string always uses the specified date type. This is the most forgiving date property type.
400
400
401
-
Date types currently supported are:
401
+
Date types currently supported by `WPDate`are:
402
402
```
403
403
dibs // 2017-02-05T17:03:13.000-03:00
404
404
secondary // Tue Jun 3 2008 11:05:30 GMT
@@ -412,6 +412,10 @@ Date types currently supported are:
412
412
dmyDashes // 30-02-2017
413
413
```
414
414
415
+
`WrapPropertyDateFormatted` (`WPDateFmt`) is initialized with a `DateFormatter` format string, so it can handle almost any date formatted as a string in a consistent way, but this also makes it fairly inflexible since the date string must closely match the date format string.
416
+
417
+
`WPDate8601` is initialized with `ISO8601DateFormatter.Options` flags. The options used along with `ISO8601DateFormatter` cover most of the variations used when working with ISO 8601 formatted date strings.
418
+
415
419
### <aname="embedded-submodel-arrays"></a>Arrays of Embedded Models
416
420
417
421
In some cases, submodels in an array are buried inside one or more subdictionaries whose only purpose is to wrap the submodel. This often happens when using GraphQL, where models can come wrapped in a "node" dictionary like this:
0 commit comments