Ivan Skriabin

A somewhat contrived use case example: ```golang // pkg1, pkg2 and pkg3 define the subsets of the FullStorage interface they need. var SharedSet = wire.NewSet( wire.Bind(new(pkg1.Storage), new(FullStorage), wire.Bind(new(pkg2.Storage), new(FullStorage), wire.Bind(new(pkg3.Storage),...

@peterbourgon What is the proper way to inject endpoint error into context? I can think only of using mutable (pointer to error interface) key in context and update it in...

Thanks, this will work for endpoint errors. But if i want to include request decoding errors as well, i will have to inject error into context in every request decoder...

Yes, it will work. But since one of the main reasons finalizer exist is logging, i really would prefer to do it there.

Thanks! This is more or less what i am trying to achieve. But, again, what is wrong with having err as an argument to finalizer? (except compatibility break)

I have a hard time grasping the concept of returning service errors inside response structure. Why do we need this if endpoint has explicit `error` return argument? How do i...

Thanks for great explanation of difference between transport and service errors. Still don't get why you prefer returning service errors inside response structure instead of using `error` return argument.

I guess that's still the bug in ModX manager, not TinyMCE package. I'm working with MODX Revolution 2.1.3-pl (traditional) and the issue can be fixed by changing the following in...

No, i simply extend from original FOS user class. In it _id_ property is protected, so there is no problem with serialization. The problem with serialization appears when it is...

I am not sure this can be classified as bug... Serializing a proxy correctly triggers __load() and object properties are loaded from DB. The problem arises from __isInitialized__ property of...