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
Is there any reason why DateTime::ISO8601 is still used in DateTimeFormatter?
Taken from the docs:
DateTime::ISO8601
DATE_ISO8601 ISO-8601 (example: 2005-08-15T15:52:01+0000) Note: This format is not compatible with ISO-8601, but is left this way for backward compatibility reasons. Use DateTime::ATOM or DATE_ATOM for compatibility with ISO-8601 instead.
DateTime::ATOM
DATE_ATOM Atom (example: 2005-08-15T15:52:01+00:00)
Is there any reason why DateTime::ISO8601 is still used in DateTimeFormatter?
Taken from the docs:
DateTime::ISO8601
DATE_ISO8601
ISO-8601 (example: 2005-08-15T15:52:01+0000)
Note: This format is not compatible with ISO-8601, but is left this way for backward compatibility reasons. Use DateTime::ATOM or DATE_ATOM for compatibility with ISO-8601 instead.
DateTime::ATOM
DATE_ATOM
Atom (example: 2005-08-15T15:52:01+00:00)
Originally posted by @geerteltink at zendframework/zend-filter#58
The text was updated successfully, but these errors were encountered: