This repository has been archived by the owner on Jan 30, 2020. It is now read-only.
DateTimeFormatter #58
Labels
Comments
|
Most likely BC compliance: changing it would be a major BC break... |
marcguyer
added a commit
to marcguyer/zend-filter
that referenced
this issue
Mar 14, 2019
* add documentation for DateTimeFormatter. Addresses zendframework#58. * add @todo notation in docblock for `$format` property * add tests for new option
marcguyer
added a commit
to marcguyer/zend-filter
that referenced
this issue
Mar 14, 2019
* add documentation for DateTimeFormatter. Addresses zendframework#58. * add @todo notation in docblock for `$format` property * add tests for new option
marcguyer
added a commit
to marcguyer/zend-filter
that referenced
this issue
Mar 14, 2019
* add documentation for DateTimeFormatter. Addresses zendframework#58. * add @todo notation in docblock for `$format` property * add tests for new option
7 tasks
|
This repository has been closed and moved to laminas/laminas-filter; a new issue has been opened at laminas/laminas-filter#7. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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)
The text was updated successfully, but these errors were encountered: