We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
All the dates from the TBA API are either unix timestamps or yyyy-mm-dd and are displayed as-is. Do some nicer parsing of dates and ranges, eg:
St. Louis, MO, USA on 2016-04-27 to 2016-04-30 should be: St. Louis, MO, USA on April 27-30, 2016
St. Louis, MO, USA on 2016-04-27 to 2016-04-30
St. Louis, MO, USA on April 27-30, 2016
Long versions of date strings may even add the day of week (short form).
The text was updated successfully, but these errors were encountered:
No branches or pull requests
All the dates from the TBA API are either unix timestamps or yyyy-mm-dd and are displayed as-is. Do some nicer parsing of dates and ranges, eg:
St. Louis, MO, USA on 2016-04-27 to 2016-04-30
should be:St. Louis, MO, USA on April 27-30, 2016
Long versions of date strings may even add the day of week (short form).
The text was updated successfully, but these errors were encountered: