feat(DateField): add parseDateFromString property
#190
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
ieromanov
force-pushed
the
feat/custor-date-from-string-parser
branch
from
d37aeac to
75411dd
Compare
|
Preview is ready. |
korvin89
reviewed
Jun 9, 2025
ieromanov
force-pushed
the
feat/custor-date-from-string-parser
branch
from
0d15b8d to
ab2ff70
Compare
|
@ieromanov One more thing, I forgot about readme. Could you add this information to all affected readme files? |
ieromanov
force-pushed
the
feat/custor-date-from-string-parser
branch
from
6b5042a to
cac61fd
Compare
|
@korvin89 take another look? I fixed everthing |
korvin89
changed the title
parseDateFromString property
korvin89
approved these changes
Jun 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
#189