payload validation for routes that have multiple method arguments

[ugate]

Is there a way to handle payload validation for routes that have multiple method arguments?

server.route({
    method: [ 'GET', 'POST' ],
    config: {
        validate: {
            payload: {
                value: Joi.string().required()
            } 
        }
    }
});

I get the following error:
Cannot validate HEAD or GET requests

v8.8.0

[mtharrison]

I would advise making those routes separately. Payload validation doesn't make sense for GET requests.

[hueniverse]

The right solution as @mtharrison said is to split it.

[ugate]

@mtharrison @hueniverse just wanted to reduce the amount of boilerplate... seems redundant to have duplicate route properties just because of one separate property, no? isn't that the point of allowing method to take an Array in the first place?

What about allowing validate to take an Array like the following?

server.route({
    method: [ 'GET', 'POST' ],
    config: {
        validate: [
            {
                query: {
                    value: Joi.string().required()
                }
            },
            {
                payload: {
                    value: Joi.string().required()
                }
            }
        ]
    }
});

...or a more explicit alternative?

server.route({
    method: [ 'GET', 'POST' ],
    config: {
        validate: {
            GET: {
                query: {
                    value: Joi.string().required()
                }
            },
            POST: {
                payload: {
                    value: Joi.string().required()
                }
            }
        }
    }
});

[hueniverse]

Method array makes sense when the routes are really identical. It is really just a shortcut and internally it is the same as adding two completely separate routes. In this case verbosity is better.

[ugate]

@hueniverse The routes are near-identical with the exception of the method and validation. the handler, path, etc. are all the same. So, verbosity in the 2nd proposed solution makes sense?

[hueniverse]

I am not going to add this. Multiple methods is a simple shortcut. If you need more, either write your own helper or just repeat the route.