gaborcsardi/parsedate issues and pull requests

#47 - Feature suggestion: Add rounding of fractional hours or minutes

Issue - State: open - Opened by billdenney about 2 months ago

#46 - Smplify parse_iso_parts

Pull Request - State: open - Opened by billdenney about 2 months ago - 1 comment

#45 - Simplify `parse_iso_parts()`

Issue - State: open - Opened by billdenney about 2 months ago

#44 - Fractional seconds are not captured

Issue - State: open - Opened by billdenney about 2 months ago - 2 comments

#43 - Fix issue with year-only date alignment

Pull Request - State: open - Opened by billdenney about 2 months ago - 2 comments

#42 - General housekeeping updates for new versions of support packages

Pull Request - State: closed - Opened by billdenney about 2 months ago - 3 comments

#41 - Docs typo fix

Pull Request - State: closed - Opened by adamhsparks over 1 year ago - 2 comments

#40 - Fix spelling in help on line 57

Pull Request - State: closed - Opened by adamhsparks over 1 year ago - 1 comment

#39 - Release parsedate 1.3.1

Issue - State: closed - Opened by gaborcsardi almost 2 years ago

#38 - Assigning wrong year to dates in the following format: month-dd-yy HH:MM

Issue - State: closed - Opened by tedmoorman over 2 years ago - 1 comment

#37 - Limitation description is not accurate.

Issue - State: open - Opened by G5W over 2 years ago

#36 - Warning when using parse_iso_8601() on a vector containing YYYY dates as well as other formats.

Issue - State: open - Opened by Esbilon over 2 years ago
Labels: bug

#35 - Release parsedate 1.3.0

Issue - State: closed - Opened by gaborcsardi over 2 years ago

#34 - No leading zero on hours leads to wrong year

Issue - State: open - Opened by sch56 about 3 years ago - 2 comments

#33 - Parsing dates with explicit time zone codes

Issue - State: open - Opened by sch56 about 3 years ago - 1 comment

#32 - Issue parsing year before 1970

Issue - State: closed - Opened by jeffreyxparker over 3 years ago - 1 comment

#31 - parse_date returns wrong/unanticipated month

Issue - State: closed - Opened by fdrennan almost 4 years ago - 1 comment

#30 - parse_date is succeptible to the 2038 bug

Issue - State: open - Opened by zkamvar over 5 years ago - 1 comment

#29 - Release 1.2.0

Issue - State: closed - Opened by gaborcsardi over 5 years ago

#28 - Change default time zone

Pull Request - State: closed - Opened by gaborcsardi over 5 years ago

#27 - WISH: New CRAN release

Issue - State: closed - Opened by HenrikBengtsson over 5 years ago - 1 comment

#26 - Date interpreted TZ incorrectly

Issue - State: closed - Opened by da11an over 5 years ago - 2 comments

#25 - Feature Request: add timezone argument

Issue - State: closed - Opened by HJAllen over 6 years ago - 4 comments

#24 - Use correct argument name "length.out"

Pull Request - State: closed - Opened by jcheng5 over 6 years ago - 2 comments

#23 - parse_date unexpected result on iso 8601 date time without second fractions

Issue - State: closed - Opened by asgeroverby almost 7 years ago

#22 - parse_date() used partial argument matching

Pull Request - State: closed - Opened by HenrikBengtsson about 7 years ago - 2 comments

#21 - getting a C_R_parse_date not found error

Issue - State: closed - Opened by Bioswami-nfac about 7 years ago - 3 comments

#20 - parse_date(character(0)) gives error

Issue - State: closed - Opened by wch about 7 years ago - 3 comments

#19 - Fix failing tests

Pull Request - State: closed - Opened by Inventitech over 7 years ago - 2 comments

#18 - Remove non-sensical input to make computation faster

Pull Request - State: closed - Opened by Inventitech over 7 years ago - 5 comments

#17 - Tests are not executed or test result does not matter

Issue - State: closed - Opened by Inventitech over 7 years ago - 1 comment

#16 - Speed up parse_date for empty input elements

Pull Request - State: closed - Opened by Inventitech over 7 years ago - 3 comments

#15 - parse_date is very slow on empty inputs

Issue - State: closed - Opened by Inventitech over 7 years ago - 5 comments

#14 - Fix spelling of versatile

Pull Request - State: closed - Opened by Inventitech over 7 years ago - 1 comment

#13 - parse_date on date before 1970

Issue - State: closed - Opened by mike-vogel about 8 years ago - 2 comments

#12 - Windows issue bad parse makes following parse bad too

Issue - State: closed - Opened by trinker over 8 years ago - 4 comments

#11 - R CMD check failures with dev version of testthat

Issue - State: closed - Opened by hadley almost 9 years ago - 3 comments

#10 - Handling of dates by parse_date() in the presence of empty strings

Issue - State: closed - Opened by plogacev over 9 years ago - 4 comments

#9 - parse_iso_8601 extremely slow

Issue - State: closed - Opened by veita over 9 years ago - 2 comments

#8 - Failure with dev version of testthat

Issue - State: closed - Opened by hadley over 9 years ago - 4 comments

#7 - fixed issue with missing prefix in regexp_to_df

Pull Request - State: closed - Opened by pieterprovoost over 9 years ago - 1 comment

#6 - Do not depend on lubridate

Issue - State: closed - Opened by gaborcsardi about 10 years ago

#5 - Non-summer dates from git are wrong

Issue - State: closed - Opened by gaborcsardi about 10 years ago - 2 comments

#4 - Git parser should give NA for numeric dates that are clearly wrong

Issue - State: closed - Opened by gaborcsardi about 10 years ago

#3 - Parsing the dreaded yymmdd date

Issue - State: closed - Opened by eddelbuettel about 10 years ago - 12 comments

#2 - Make compilation work on windows

Issue - State: closed - Opened by gaborcsardi about 10 years ago - 1 comment

#1 - Git parser should fill in zeros

Issue - State: closed - Opened by gaborcsardi about 10 years ago - 3 comments

GitHub / gaborcsardi/parsedate issues and pull requests