null VS validator

Use-case: working on PATCH requests, the body may or may not contain nullable values. I am using guregu/null and I can't use a pointer because if the json contains "null" as a value, the pointer will be set to nil in the struct, instead of a value representing the presence of null. In short I can't differentiate the absence of the field in the request from the presence of the field with a null value.

https://github.com/guregu/null is an awesome package implementing most SQL scanner Interfaces plus JSON

There’s also this: https://github.com/guregu/null

Unfortunately in Go, switching to *bool makes the api a little more awkward to use since users that need to set true or false have to define a local variable then use a pointer to that. Another option would be something like null, but that adds a dependency to your currently-dependency-free project. If anyone has a better solution to this pattern, I'd love to hear it.

(That's how certain kinds of extensibility work in the validator crate. You just impl a method and validator won't care where it comes from as long as it's in scope because it's built using declarative macros.)

The rust proc macro system is my absolute favorite feature of the language. One of my other favorite libraries is https://github.com/Keats/validator

Hi! I'm happy to announce the release of garde. In summary, this is a rewrite of the validator crate.

Validator : Macros 1.1 custom derive to simplify struct validation inspired by marshmallow and Django validators

https://github.com/Keats/validator needs some help, it's a validation library that easily plugs into Web Development.

(The validate attribute is from the validator crate.)

Would love to use it in https://github.com/Keats/validator when it's ready!

Actually, /u/mehcode just reminded me that this exists: https://github.com/Keats/validator