You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following the example of Chronic gem for Ruby, it would be great for the library to have an option to return a date range based on the precision of entry. Here are some examples of what inputs/outputs would look like:
Thanks for the suggestion, but I'm not convinced that the usefulness of this feature outweighs the complexity. Have you used this feature in chronic? Can you give me an example use case?
Yep, I'm using the described feature in Chronic. The usefulness comes from ability to recognize precision - imagine entering "June 2, 2010" for an all-day event in your calendar vs. entering "June 2, 2010 12:00am" for one at a specified time. Currently, there is no way to recognize the difference.
Following the example of Chronic gem for Ruby, it would be great for the library to have an option to return a date range based on the precision of entry. Here are some examples of what inputs/outputs would look like:
"Jan 20, 2010 9:10pm" => "Jan 20, 2010 9:10:00pm" to "Jan 20, 2010 9:10:59pm"
"Jan 20, 2010 9pm" => "Jan 20, 2010 9:00:00pm" to "Jan 20, 2010 9:59:59pm"
"Jan 20, 2010" => "Jan 20, 2010 00:00:00am" to "Jan 20, 2010 11:59:59pm"
"Jan 2010" => "Jan 1, 2010 00:00:00am" to "Jan 31, 2010 11:59:59pm"
"2010" => "Jan 1, 2010 00:00:00am" to "Dec 31, 2010 11:59:59pm"
The text was updated successfully, but these errors were encountered: