Pavel Kutáč

- [ ] Added or updated tests - [ ] Documented user facing changes **Changes** The documentation mention, we should be using `BelongsTo` but when I use it, I got...

Linter to disallow struct initialization without field names

5

**Is your feature request related to a problem? Please describe.** Go allows you to initialize struct only by values, if they follow same order as in structure definition. This can...

You did really good piece of library. I was using that since beginning and you also implemented some of my suggestions. But seems, you do not have time to maintain...

Is there a way not to include name of Embedded structure in Namespace for error?

5

We are using Validator to validate incoming JSON requests. And because all requests contains common attributes we are using embedding (`Human` in the example below). Since that embedding has no...

Element is null, which is not allowed error when errors are added to context only

1

I'm getting error `the requested element is null which the schema does not allow` when adding errors to the GraphQL context and `return nil, nil` from resolver. I have this...

**Is your feature request related to a problem? Please describe.** Currently I specify data type by structure name. Like this ```go // @Failure 404 {object} api.ErrorResponse ``` But in my...

Feat: add tag to skip namespace in embedded structures

3

## Enhances Introducing new `skipns` validate tag, that allows to skip the name of embedded struct, when printing invalid field namspace. ```go type Outer struct { Embedded `validate:"skipns"` } ```...

Add Unwrap methods for bolt errors

3

Error types are in internal package, so casting is not possible. And because of missing `Unwrap` method, the `errors.Is()` doesn't work either. Closing #631

Missing Unwrap function for internal bolt errors

1

We are using latest driver v5, and when context is cancelled, the error returned from the `ExecuteRead` or similar function is `ConnectionReadCanceled` etc. It is in internal package (neo4j/internal/errorutil/bolt.go), so...

**Describe the bug** When you use `fx.Annotate` together with ```fx.ResultTags(`group:"name"`)```, but return different types in different places, it is very easy to ignore some of them. Because if you have...