Looks like the API documentation has not been regenerated since 3.0.2, as the maxBodySize value typo is still present here:

https://api.vapor.codes/vapor/latest/Vapor/Structs/NIOServerConfig.html#/s:5Vapor15NIOServerConfigV7defaultACSS8hostname_Si4portSi7backlogSi11workerCountSi11maxBodySizeSb12reuseAddressSb10tcpNoDelaytFZ

Describe the bug
The default port for a Sanic app is 8000, which by HTTP standards is a custom port. This port can also be set during calls to app.run().

When using app.url_for('handler.name', _external=True), the resultant URL does not contain the port without manual intervention.

This line is the final step before the application returns the URL. The URL is build using `urlunp

Description

I'm submitting a feature request (I intend to work on this myself if I can find the time).

While Option<Callback> works as expected (the prop takes a closure and defaults to None), that doesn't really apply to other Option<T> properties, leading to a small amount of boilerplate (which might accumulate quickly).

For example: If I have a property of type `Option<S

The documentation of FromDataSimple doesn't mention that it's only for debugging. This is only mentioned at documentation of FromData.

Based on several closed issued about this and recent message at #beginners, this causes enough confusion that documentation of FromDataSimple should also mention this.

Describe the feature
Adopt opencensus for metrics and tracing

Additional context
https://opencensus.io/

As of now the API page is pretty bland and nothing in the config page is actually explained.

Obviously some things should be obvious like what "port" changes, but somethings aren't exactly 100% such as host_binding or server, I guess to some its obvious while as to others it isn't. Either way i think this page and some others could use some more i

Express allows debugging by setting DEBUG=express:* as described in https://expressjs.com/en/guide/debugging.html.

After activating the debug messages, it is possible to see the middleware being called in the console as, for example:

express:router dispatching GET /v1/users/?page=1&limit=100 +3s
express:router query  : /v1/users/?p

Description

Document all of the amber codebase to be compatible with crystal docs and generate a nice web api page

Steps to Reproduce

Not applicable (feature request)

Versions

Master amberframework/amber@bea1063

Additional Information

We can host the new api page on amberframework.org/api as well :+

Issue Description

I would love to see (or write) a guide on how to migrate a WIP project from SailsJS (since it's based on that) to TrailsJS. If possible.

Environment

• node version: 6.X
• trails version: latest
• operating system: Ubuntu 16.04 64 bits

When running your app through lucky dev, there's no way to pass --error-trace currently. We need a way to proxy that down to this command.

We could have lucky dev --error-trace or maybe you just edit your Procfile.dev (which would probably need to happen anyway), and update lucky watch --error-trace.