feat(locale): 🎸 add dateRange pipe #764
Open
Conversation
This file contains 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
Implementation of the Intl.DateTimeFormat.prototype.formatRange() method BREAKING CHANGE: 🧨 addition of ES2021.Intl into the typescript configuration ✅ Closes: jsverse#763
|
any plan to get this merged? |
|
@denisyilmaz Hey, sorry for not replying I'm currently unavailable. There might be another breaking change introduced in #768 so I think we will release both together as all the other libraries are bumped as well. |
- feat: fallback to single date translocoDate pipe if no endDate - fix: linting
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.
Implementation of the Intl.DateTimeFormat.prototype.formatRange() method
BREAKING CHANGE: 🧨 addition of ES2021.Intl into the typescript configuration
✅ Closes: #763
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information