ᴊᴏᴇ ᴄʜᴇɴ
ᴊᴏᴇ ᴄʜᴇɴ
Hi, thanks for the idea! But I would recommend user makes the struct implements an interface and do customized validation in the user-defined method.
No, what I meant is user implements interface with methods, for example `MapVaildation` and `RefecltValiddation`. You write validation logic but you don't call them.
It will look like `(s *Struct) MapValidation(filedName string, value interface{}) error`.
OK, I can accept: ```go type Person struct { Name string `regexp:"^\d+$"` // Go Regexp here } ``` But no funcs, it is not a good idea from my perspective.
If you already have `MapValidation`, there is no need to add tags, that's more confusing.
Maybe we should just add similar thing as https://go-macaron.com/docs/middlewares/binding#validate
Basically, yes.
Seems not much resources can be found about Go flock... - https://github.com/nightlyone/lockfile - https://gist.github.com/jedy/4167513 Not sure how well they work cross-platform.
Hi, thanks for the good idea, but unfortunately it's not supported yet. Will consider such functionality..
In a second thought, what is your definition of **custom types**?