ozzo-validation
zap
ozzo-validation | zap | |
---|---|---|
13 | 51 | |
3,580 | 21,002 | |
1.3% | 1.1% | |
0.0 | 8.1 | |
about 2 months ago | 11 days ago | |
Go | Go | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ozzo-validation
-
Is there any equivalent to pydantic, serde, etc?
go-ozzo/ozzo-validation
- Request Validations in Go REST API
-
Suggestion for a dynamic Struct Validation Rules
https://github.com/go-ozzo/ozzo-validation Seems to do what I need but likely will need some convoluted reflection to build out the rules. Also likely some custom rules to be written which is okay since it's a one time cost and reuse in the expressions.
-
Proper validation package suggestion
Personally I use ozzo validation: https://github.com/go-ozzo/ozzo-validation
-
Valgo is a type-safe, expressive, and extensible validator library for Golang.
This looks useful, but what differentiates it from something like https://github.com/go-ozzo/ozzo-validation ? Why would I use Valgo over something battle tested that follows a very similar pattern?
-
Why use go over node?
This is where it gets spicy: I just don't get at all who ever though this struct-tag based validation library was a good idea https://github.com/go-playground/validator - and yet it's the most mainstream one. Try to implement your own type, you're up to register some global validation tag and repeat it every time you're using that type. I'm grateful https://github.com/go-ozzo/ozzo-validation exists, that's what I use. But it's still way behind the other things I mention, where in general, it's simply not possible to pass around an invalid struct - because it can't be built if it's invalid in the first place.
-
Gin vs Echo framework
Gin comes with built-in "validation", while Echo recommends the same validator. I am also not a fan of magic struct tags, so I would probably prefer either writing my own or using something like ozzo.
-
What type of software do you write at your workplace?
Other packages of note: https://github.com/uber-go/zap https://github.com/go-ozzo/ozzo-validation
-
is there any package to generate validation code for struct instead of using reflect (tags)?
Does https://github.com/go-ozzo/ozzo-validation meet your requirements?
-
How do you validate your structures?
https://github.com/go-ozzo/ozzo-validation/blob/v3.6.0/struct.go#L61
zap
- Desvendando o package fmt do Go
-
Building RESTful API with Hexagonal Architecture in Go
The project currently uses slog package from standard library for logging. But switching to a more advanced logger like zap could offer more flexibility and features.
-
Structured Logging with Slog
It's nice to have this in the standard library, but it doesn't solve any existing pain points around structured log metadata and contexts. We use zap [0] and store a zap logger on the request context which allows different parts of the request pipeline to log with things like tenantid, traceId, and correlationId automatically appended. But getting a logger off the context is annoying, leads to inconsistent logging practices, and creates a logger dependency throughout most of our Go code.
[0] https://github.com/uber-go/zap
-
Kubebuilder Tips and Tricks
Kubebuilder, like much of the k8s ecosystem, utilizes zap for logging. Out of the box, the Kubebuilder zap configuration outputs a timestamp for each log, which gets formatted using scientific notation. This makes it difficult for me to read the time of an event just by glancing at it. Personally, I prefer ISO 8601, so let's change it!
-
Go 1.21 Released
What else would you expect from a structured logging package?
To me it absolutely makes sense as the default and standard for 99% of applications, and the API isn't much unlike something like Zap[0] (a popular Go structured logger).
The attributes aren't an "arbitrary" concept, they're a completely normal concept for structured loggers. Groups are maybe less standard, but reasonable nevertheless.
I'm not sure if you're aware that this is specifically a structured logging package. There already is a "simple" logging package[1] in the sodlib, and has been for ages, and isn't particularly fast either to my knowledge. If you want really fast you take a library (which would also make sure to optimize allocations heavily).
[0]: https://pkg.go.dev/go.uber.org/zap
[1]: https://pkg.go.dev/log
- Efficient logging in Go?
-
Why elixir over Golang
And finally for structured logging: https://github.com/uber-go/zap
-
Beginner-friendly API made with Go following hexagonal architecture.
For logging: I recommend using Uber Zap https://github.com/uber-go/zap It will log stack backtraces and makes it super easy to debug errors when deployed. I typically log in the business logic and not below. And log at the entry for failures to start the system. Maybe not necessary for this example, but it’s an essential piece of any API backend.
- slogx - slog package extensions and middlewares
- Why it is so weirdo??
What are some alternatives?
validator - :100:Go Struct and Field validation, including Cross Field, Cross Struct, Map, Slice and Array diving
logrus - Structured, pluggable logging for Go.
Password validator library for Go - Flexible and customizable password validation
zerolog - Zero Allocation JSON Logger
govalidator - [Go] Package of validators and sanitizers for strings, numerics, slices and structs
slog
Validate - ⚔ Go package for data validation and filtering. support Map, Struct, Form data. Go通用的数据验证与过滤库,使用简单,内置大部分常用验证、过滤器,支持自定义验证器、自定义消息、字段翻译。
glog - Leveled execution logs for Go
protoc-gen-validate - Protocol Buffer Validation - Being replaced by github.com/bufbuild/protovalidate
go-log - a golang log lib supports level and multi handlers
postcode - Small Golang package for validating postal codes
log - Structured logging package for Go.