Closed tkettani closed 3 years ago
hey @tkettani sorry didn't got a message about the issue. Yeah i haven't tried it with nullable types. Thanks for the pull request. I'll appreciate the input but I've added a new version that would split the component repos, so i close the pull request. . I'll take a look and incorporate your suggestion in the next version. I'm still in the progress of setting up the development pipeline and documentation. Take a look at the new master. That would render your ENUM (i assume) list redundant.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Hi, I have the same problem. When this will be fixed?
this is already addressed in 0.4.0. So update to latest or if you have 0.4.0 you may have found a new bug: create an issue with the reproduction steps.
Hello thanks for the great work on this library i just came across an issue, when one of my POCO fields is a nullable type (int?, bool? etc) i get this error:
by the way in my startup i am defining the initial setup as such:
thanks for any help or pointers on how to go around this issue. cheers from Canada !!