-
Notifications
You must be signed in to change notification settings - Fork 55
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.
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
Use instance instead of JsonConvert class #14
Comments
I'll close this as this is implemented now. Will publish the NPM package when the other features are included as well. |
Thanks a lot. Congratulations for your 1.0.0 release ! |
Thanks, but no release done yet. We are still testing some things ;-) Have a look at it, if you like to. |
Haha, I hadn't noticed it wasn't really released yet. It's a major step in the right direction anyway. I just wanted to congratulate you :) |
Yes we'll hopefully be able to release it soon. Cheers |
Hello,
I just found this package and I'd like to thank and congratulate you for your work.
However I've got a few concerns before it actually matches all my needs. Two of these concerns are already covered by issues #4 and #6 . My last (minor) concern is about converter configuration.
Here is what bothers me.
In my project there are two kinds of JSON that I will use. In one of them, the null values are perfectly fine. In the other one, null values are forbidden. And since the configuration is set at
JsonConvert
class level, I need to set the value checking mode at each use.For instance:
It means that my code spends time resetting the configuration every single time I use the converter.
I think it could be interesting to consider moving all the configurations and the methods to instances.
For example:
This issue is probably not of the highest priority, and could be discarded completely, but I thought I should share with you my perspective on things.
The text was updated successfully, but these errors were encountered: