Skip to content

Issues: robertwilczynski/nChronic

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.

Sign up for GitHub

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

17 Open 3 Closed
17 Open 3 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Request - Parse common financial maturities
#28 opened Nov 19, 2017 by ckarcz
Wrong time when parsing "today at midday"
#27 opened Nov 14, 2017 by clari182
{Time} + {Date} often not parsed
#26 opened Nov 3, 2017 by ghost
Invalid dates incorrectly parsed when month name specified
#25 opened Jun 15, 2017 by kurthamilton
Support to pt-BR
#24 opened May 17, 2017 by rcarubbi
1
"5 to 6 June" not parsed
#23 opened Mar 29, 2017 by LTsLlama
Global EndianPrecedence configuration isn't available
#20 opened Mar 13, 2017 by adebisi-fa
Can't parse a string containing DateTime.MaxValue
#19 opened Mar 2, 2017 by codenjs
1
Evaluating current year versus next year
#18 opened Dec 2, 2016 by wbreza
Support for .NET Core
#16 opened Aug 11, 2016 by kant2002
2
"next year" and "in one year" should evaluate to the same date and time
#15 opened Jul 12, 2016 by icnocop
parser.Parse shouldn't throw exception on null parameter.
#13 opened Jul 3, 2016 by MNF
1
Could you please add strong names and signing?
#12 opened Mar 30, 2016 by chrimc62
2
NuGet package updated to version 0.3.1 but assembly (file) version is still 0.2.1
#11 opened Feb 24, 2016 by icnocop
Add support for TryParse
#10 opened Jan 13, 2016 by ramiabughazaleh
"Day after tomorrow" not parsed
#7 opened May 7, 2015 by kundusandeepan
3
"7 weeks and 6 days from now" not parsed correctly bug customer-request
#3 opened Apr 11, 2012 by robertwilczynski
@robertwilczynski
1
ProTip! Type g p on any issue or pull request to go back to the pull request listing page.