Daniel Francesconi
Daniel Francesconi
Any updates on this issue?
Experiencing the same issue.
Same for: https://gocover.io/github.com/francesconi/go-rampart Package: https://pkg.go.dev/github.com/francesconi/go-rampart
Would need this as well.
Let's say you have a custom error with a dynamic string ``` type NotFoundError struct { File string } func (e *NotFoundError) Error() string { return fmt.Sprintf("file %q not found",...
Based on the previous example something like this _(untested)_ ``` type Foo struct { File string } func (f *Foo) Schema(whitelist []string) v.Schema { return v.Schema{ v.F("file", p.File): v.In(whitelist).Err(&NotFoundError{File: p.File}),...
The whole point about this is matching an error with a dynamic string ``` type Foo struct { File string } func (f *Foo) Schema(whitelist []string) v.Schema { return v.Schema{...
I've just had a look into [Google API's Error Design](https://cloud.google.com/apis/design/errors#error_model) about error details and I must admit that they would work fine for me :thumbsup:
A client sends us availabilities for it's hotel rooms. When a certain room does not exists on our side `RoomNotFound` I can request the client to resend me all rooms...
Would be enough if one room is missing but if more rooms are missing i'll get duplicate error messages ``` // Output: // err[0]: INVALID(room not found) // err[1]: INVALID(room...