res.negotiate()
This method is deprecated.
You should use a custom response instead.
To handle errors from Waterline model methods, check the
nameproperty of the error (see the Waterline error reference for more details).
Given an error (err), attempt to guess which error response should be called (badRequest, forbidden, notFound, or serverError) by inspecting the status property. If err is not a dictionary, or the status property does not match a known HTTP status code, then default to serverError.
Especially handy for handling potential validation errors from Model.create() or Model.update().
Usage
return res.negotiate(err);
Details
Like the other built-in custom response modules, the behavior of this method is customizable.
res.negotiate() examines the provided error (err) and determines the appropriate error-handling behavior from one of the following methods:
res.badRequest()(400)res.forbidden()(403)res.notFound()(404)res.serverError()(500)
The determination is made based on err's "status" property. If a more specific diagnosis cannot be determined (e.g. err doesn't have a "status" property, or it's a string), Sails will default to res.serverError().
Example
// Add Fido's birthday to the database:
Pet.update({name: 'fido'})
.set({birthday: new Date('01/01/2010')})
.exec(function (err, fido) {
if (err) return res.negotiate(err);
return res.ok(fido);
});
Notes
- This method is terminal, meaning it is generally the last line of code your app should run for a given request (hence the advisory usage of
returnthroughout these docs).res.negotiate()(like other userland response methods) can be overridden - just define a response module (/responses/negotiate.js) and export a function definition.- This method is used as the default handler for uncaught errors in Sails. That means it is called automatically if an error is thrown in any request handling code, but only within the initial step of the event loop. You should always specifically handle errors that might arise in callbacks/promises from asynchronous code.
For a better experience on sailsjs.com, update your browser.
Reference
- Application
- Blueprint API
- Command-line interface
-
Configuration
- sails.config.*
- sails.config.blueprints
- sails.config.bootstrap()
- sails.config.custom
- sails.config.datastores
- sails.config.globals
- sails.config.http
- sails.config.i18n
- sails.config.log
- sails.config.models
- sails.config.policies
- sails.config.routes
- sails.config.security
- sails.config.session
- sails.config.sockets
- sails.config.views
-
Request (`req`)
- req._startTime
- req.body
- req.cookies
- req.fresh
- req.headers
- req.hostname
- req.ip
- req.ips
- req.isSocket
- req.method
- req.options
- req.originalUrl
- req.params
- req.path
- req.protocol
- req.query
- req.secure
- req.signedCookies
- req.socket
- req.subdomains
- req.url
- req.wantsJSON
- req.xhr
- req.accepts()
- req.acceptsCharsets()
- req.acceptsLanguages()
- req.allParams()
- req.file()
- req.get()
- req.is()
- req.param()
- req.setLocale()
- req.setTimeout()
- req.host
- Response (`res`)
- Waterline (ORM)
- WebSockets
Reference
Built with Love
The Sails framework is built by a web & mobile shop in Austin, TX, with the help of our contributors. We created Sails in 2012 to assist us on Node.js projects. Naturally we open-sourced it. We hope it makes your life a little bit easier!
© 2012-2024 The Sails Company.
The Sails framework is free and open-source under the MIT License.
Illustrations by Edamame.