-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
weird response #44
Comments
Good idea, I take a look tomorrow |
If you like I can do a pull request. I like the first part of my previous response, but the part of errors (with other code param), do you like this part? do you think in other solution better? |
Yes, you can provide a pull request : I'm a little bit overloaded these days |
I was checking yesterday the library. In my project I was working with the version 0.1.0, but now is in 1.0.5. This was the main problem, my main problem. In this version, the node-restify-validation library, implements fine the restify error handler, and I can get similar errors like restify. Now, Restify with restify-validation 1.0.5 error response is cool:
Anyway, I think that will be better something like:
What do you think? @gchauvet |
It would be interessting to normalize node-restify-validation like restify. I working on this today. |
If you are using Restify, the normal error have this schema example:
Have code and message.
But in restify-validator you can get something like this:
As you can see, no there are any first level code param, and there are a status param. That is the first time that I see.
Maybe will be maintain the same schema:
The main idea is maintain a similar schema of Restify
The text was updated successfully, but these errors were encountered: