Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Maybe<DateTime> doesn't work
See original GitHub issueHi!
I’m trying to have optional DateTime. But when I do Maybe<DateTime>.None, it uses the default value which is 0001-01-01, and when I do .HasValue, it’s true.
Thanks !
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Trouble with datetime - python
The issue starts with the .strptime(). I am unable to convert start_date into format that strptime will accept. Yes, I have read many...
Read more >System.DateTime doesn't recognize it's own format?
Contrary to the behavior on my laptop, on Android when this line is executed I get the error "FormatException: String was not recognized...
Read more >Solved: VA format is not working with parsing a datetime
Solved: I have a date time in a CSV, and VA recognizes it as a character when I upload the csv. Okay, so...
Read more >DateTime format error getting data from PBI DataFlow
This is an issue where datetime fields in PBI DataFlow Entities load/refresh and display correctly. In PBI Desktop, if use the DataFlow as...
Read more >Using Python datetime to Work With Dates and Times
Have you ever wondered about working with dates and times in Python? In this tutorial, you'll learn all about the built-in Python datetime...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@robosek Hmm ok. I thought the Maybe monad was to encapsulate either a value, or nothing.
And I’m more confused with the end of the discussion of #28 with “it makes sense to remove this limitation in order to enable fluent syntax with .NET value types.”.
@paparent this issue was resolved with Issue #67 and now
Maybe<DateTime>.Noneworks correctly