Releases: bouwe77/temba
v0.32.0
v0.31.0
New feature
Internal Temba logging now logs on either debug, info, or warn level to the console.
The log level can be configured through the environment variable LOG_LEVEL, example:
LOG_LEVEL=info
The default LOG_LEVEL is debug, so nothing really changed in what was logged before.
v0.30.3
v0.30.2
v0.30.1
v0.30.0
New feature
The requestInterceptor now also intercepts GET and DELETE requests.
Depending on what Temba supports per method, a requestBody is available in the callback, or not.
This also means that the id will be passed to the interceptor callback as well. Not only for the new GET and DELETE interceptors, but also for the existing PUT and PATCH interceptors.
v0.29.0
Breaking change
Providing IDs in the request body of POST, PUT, or PATCH requests is not allowed and will return a 400 Bad Request response. The same applies to adding an ID in a POST request URL, or omitting an ID in a PUT or PATCH request URL.
Until now, IDs in request URLs and request bodies were ignored, and for missing IDs in URLs a 404 Not Found was returned.
Now this has been unified to a 400 Bad Request, because you are trying something that isn't supported, so let's be clear about that.
v0.28.0
v0.27.0
Breaking change
From now on, a DELETE on a collection, which deletes all items on the collection, is no longer the default.
Example request:
DELETE /movies
From now on, by default, this will return a 405 Method Not Allowed response.
If you want to allow deleting entire collections, set the allowDeleteCollection setting to true:
const config = {
allowDeleteCollection: true,
}
const server = temba.create(config)
With this setting, a DELETE request to /movies will delete all movies, and a 204 No Content response will be returned.