[Core][RFC] Refactor/date types #287
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was originally copied from Symfony, but because this transformer was only used for norm-input which is mostly API provided JSON support for this format is not really needed. The option was removed, but RFC3339 actually supports this, not not vice-versa.
sstok
force-pushed
the
refactor/date-types
branch
from
5c6bf4a to
ba9cb62
Compare
Member
Author
|
Oh... the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 makes the model-format of the Date(Time) types immutable, and removes support for HTML5 input format for norm-input (which is actually less flexible than RFC3339).