Please use the excellent work in #1511 for the missing documentation (the relevant parts, modified to this style).

@hueniverse updated

I didn't mean to create a new file like methods.js which made sense because it had a lot of other logic. Just mean that the handlers definitions should be owned by the pack.

The docs still show passing the schema as a third argument to handler() which I don't want. I want the method itself to do this.

Also, cannot override the built-ins.

OK - will pull it back into pack.js.

Just so we're clear, this means that any new handlers will use Joi.any(), right?

The initial issue called for the ability to override the built-ins. Is it safe to assume that no handlers can be overridden once they are defined?

Yes, no overrides. First win.

New handlers will need to verify the config using whatever they want, but the route handler config must still be an object with a single key that is Joi.object().

@hueniverse one more time

Closed?

The way my code is currently set up, moving the schema validation into the handler generator is going to take some restructuring. If you look at my tests, I was expecting the user to pass in the handler generator. By making this change, non-builtins need to be wrapped at runtime. Also, by eliminating the third schema argument, the Pack.prototype._handler() function has to give the builtins special treatment. It's starting to seem a bit hacky.

Ok. I'll give it a pass tonight so you can see what I mean.

@hueniverse is this what you meant?