André Eriksson

This looks great, thank you @Minivera!

Thanks @Minivera! For this to show up in the Encore website docs it needs to be added to the `docs.cue` file, at the end of the `how-to` section. If you...

Hi @derkan, thanks for asking. It would be very helpful to better understand your use case. Encore is primarily designed for building cloud native applications; could you share a bit...

This is a great idea. We should definitely support something like this. Thanks very much for the detailed explanation and rationale!

Thanks @azr for the kind words! Yes, we definitely want to add support for additional transport protocols, with gRPC being the primary choice :)

This sounds great! After some consideration I think a dio-specific generator is going to be easier to manage going forward than a pluggable one. What do you think?

Thanks @gmlewis! Those are really good points. We definitely want to improve the usefulness of the API docs for raw endpoints, so we'll take a look at fixing this. And...

I think something like that would be a great addition, for several reasons. The other reason to support something like this is to be able to see the code that...

I've made a fair bit of progress on this. I think it should be workable. The current design I am thinking of is the following. Let me know what you...

Something like this for net/http: ``` go func DiscoverHTTPGet(d *discover.D) { ts := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) { fmt.Fprintln(w, "Hello, world") })) defer ts.Close() d.Trace(func() { res, err := http.Get(ts.URL)...