devin ivy
devin ivy
Resolved with v21 https://github.com/hapijs/hapi/issues/4386
> Eg. there is no way to localize the generated error. > > keep the false as it is and do some special treatment during the validation, but it has...
Adding to the release notes 👍
I believe that this is a new feature augmenting the existing query parser functionality: https://github.com/efbenson/hapi/commit/5903cd510bc2dd47d3289e2089f2838fb9a9df27#diff-f6078640b332d9e3a509ffc552a2fb79cb93f7f0c1fb99bc6d23ccb195fd22a9R793-R801 Seems like a valid feature request, has also been mentioned in the past here: https://github.com/hapijs/hapi/issues/4058....
That's a good thought. Another approach could be to tack the default error onto the detailed error in this case so that it could be accessed: ```js failAction(request, h, err)...
Resolved with v21 https://github.com/hapijs/hapi/issues/4386
Hey, thanks for the report. I will take a look at this some time today, but if you can see what's wrong we'd certainly accept a PR!
Can you help me understand the merits of a 200 versus a 204? I'm not terribly worried about the 19 bytes, but I do wonder if we'd be going against...
> The point is that 200 works everywhere, and is likely to continue doing so forever, while 204 can break in some configurations. Ahh I see— I haven't been able...
Resolved with v21 https://github.com/hapijs/hapi/issues/4386