A user can easily serve a static file in an annotated service as follows:

@Get("...")
@Head("...")
HttpResponse getFile(ServiceRequestContext ctx) {
    return HttpFile.of(...).asService().serve(ctx, ctx.request());
}

However, it'd be even nicer if a user can do this:

@Get("...")
@Head("...")
HttpFile getFile() {
    return HttpFile.of(...);
}

Is your feature request related to a problem? Please describe.

As observed during #261, users can accidentally set timeouts inconsistently. A concrete example is that one can set a User facing timeout lower than any backend timeout, such that requests may fail early.

Describe the solution you'd like

We should provide some sanity checking to prevent unintended timeout behavior.

I'd love to use mercurius instead of apollo-server-lambda, so if someone has done this, please contribute even a short guide.

Enterprise Gateway documentation spans various roles and forms for information. It would be helpful to have this reorganized based on a consumer's role. Something similar to how the Jupyter Server or Zero to JupyterHub docs would be nice.

Sections for