Skip to content
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

Find answer for date functions and year outputs #183

Open
rdmurphy opened this issue May 20, 2020 · 0 comments
Open

Find answer for date functions and year outputs #183

rdmurphy opened this issue May 20, 2020 · 0 comments
Milestone

Comments

@rdmurphy
Copy link
Owner

This would be a breaking change if done.

Frankly in the majority of scenarios that I'm attempting to use apdate the very first thing I do is peel off the , YEAR that's at the end of the string. Would it make sense for it to stop doing it entirely, or to make it a flag?

Originally it was going to be "smart" and only include it if the input date isn't current year, but I worried that was too clever.

Any input would be appreciated. 👋

@rdmurphy rdmurphy changed the title Should apdate continue outputting the year? Find answer for date functions and year outputs Jan 6, 2023
@rdmurphy rdmurphy added this to the v3 milestone Jan 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant