Raphael Simon

That makes a lot of sense! A goal of the Goa design is to ensure that design code is never used at runtime, the DSL is only used for code...

This is great, considering only the "transport-agnostic" scenario for a moment the use cases that this would need to support are: 1. A middleware that modifies the request payload 2....

>What do you think of some mechanism to allow “type safe” interaction with context? My knee-jerk reaction would be that this would be out-of-scope of Goa. Different use cases might...

Hello! Great conversation, I spent a bit of time going through various options and here is a concrete proposal that would fit well with the current design of Goa. #...

The same way it gets generated today. The point being that the data structure used by the OpenAPI generator would correctly reflect the transport level layout.

I updated the proposal to illustrate a nice benefit of interceptors: they make is possible to inject user code in the marshalling/unmarshalling phase. This is pretty powerful as it has...

Completely agree with all these points @tchssk! Let's iterate on the proposal to tackle these limitations, I have a few ideas. Also I'm thinking it would be better to break...

Just a note that there is indeed a bug in that Goa should never panic. That being said the correct DSL here would be: ```go var _ = Service("products", func()...

Yes you are correct, the name of the path param needs to match the name of the attribute. The idea is that the name of the path params should not...

That's fair, it does set the expectation. I guess the one place where that might matter is in the generated OpenAPI specification. I'm reopening the issue so we can add...