-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
make date autoformatting (duplicate 2nd line omission) configurable #3108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Yes, very useful. It is absolutely critical for international applications. |
@markzolotoy interesting, can you say more about why this becomes more important internationally? I agree that it's a useful feature, but the implication of your comment is that the labels are actually wrong, or unintelligible perhaps, with automatic duplicate pruning in other languages/calendars? |
When using default date formatting which for US dates it is working in that way. But try to achieve the same for any foreign date such as French or Chinese. Since our app. allows our customers flip between languages it is critical that it looks and feels exactly the same in every language. |
Another use case for this is one I have - I'd like to show the weekday in that date format part, which is very important for my use case, but I also don't want that to be repeated on every time tick. I think the line that causes this is: Line 474 in 30ed4a4
Would be very grateful for some way to customise or work around this (even if a workaround is to somehow override the |
Hi - this issue has been sitting for a while, so as part of our effort to tidy up our public repositories I'm going to close it. If it's still a concern, we'd be grateful if you could open a new issue (with a short reproducible example if appropriate) so that we can add it to our stack. Cheers - @gvwilson |
When using properly formatted dates in the default format the second line is automatically omitted after the first tick if it doesn’t change.
tickformat
is applied as well.The text was updated successfully, but these errors were encountered: