-
Notifications
You must be signed in to change notification settings - Fork 8
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
Custom date format broken after latest update #17
Comments
v2.0.0 is a major semver change and implies breaking changes. I switched to a different date library. You can see the options in the README: https://github.com/dannyfritz/atom-date#options |
I double checked your readme in Atom and it should still work for my
format. Perhaps that needs to be updated as well.
…On Sep 20, 2017 9:43 PM, "Danny Fritz" ***@***.***> wrote:
v2.0.0 is a major semver change and implies breaking changes.
I switched to a different date library. You can see the options in the
README: https://github.com/dannyfritz/atom-date#options
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#17 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABf-ljCrW3qtYg2jH-ayWYfIiW-s7J59ks5skc1ZgaJpZM4Pedig>
.
|
According to the docs it should be: |
Oh, I see what you are saying. I'll have to publish a change to the README once I get to my computer. |
Closed
Cool, thanks!
…On Sep 20, 2017 10:33 PM, "Danny Fritz" ***@***.***> wrote:
Oh, I see what you are saying. I'll have to publish a change to the README
once I get to my computer.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#17 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABf-lqqKillfkrYxXwjKOTCuOKu-3uIuks5skdkOgaJpZM4Pedig>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have the following custom date format:
Before I updated to version 2.0.0 this resulted in dates that looked like:
After the update, the same formatter spits out:
The text was updated successfully, but these errors were encountered: