Skip to content

Releases: skelpo/APIErrorMiddleware

v0.3.5

24 Jul 09:18
c8cd6bd
Compare
Choose a tag to compare

Compilation error fix!

v0.3.4

23 Jul 07:16
bd4cead
Compare
Choose a tag to compare

Custom headers are now supported! Thanks @Cellane !

v0.3.3

29 May 12:59
2025900
Compare
Choose a tag to compare

Error JSON Encoding Failure Error

Instead of having an empty body for the response body when JSON encoding fails, we use a string value that tells you what went wrong.

v0.3.2

25 May 13:05
36a1568
Compare
Choose a tag to compare

Debug the Debuggable

Added a case to the error conditions in the APIErrorMIddleware responder for Debuggable errors when the app is in a dev environment.

Also added a compiler conditional so you don't get warnings about casting an Error to CustomStringConvertible always succeeding. Because it doesn't. On Linux that is.

Fix for linux

09 May 14:57
Compare
Choose a tag to compare

For some reason linux throws "APIErrorMiddleware.swift:92:31: error: 'Error' is not convertible to 'CustomStringConvertible'; did you mean to use 'as!' to force downcast?".

This is not fixed though it generates a warning for Mac. The warning is of no meaning though.

v0.3.0

07 May 19:28
Compare
Choose a tag to compare

The 3rd Vapor

Now uses the official 3.0 release of Vapor 💪.

v0.2.2

03 May 12:24
Compare
Choose a tag to compare

If the Promise don't Succeed, Try, Try Again.

Apparently returning the result of next.respond(to:) was a bad idea, so now we only return response.futureResult. We don't have errors escaping the middleware anymore 🙂.

v0.2.1

03 May 12:20
Compare
Choose a tag to compare

Fixed Bad Synth

Public structs don't get public synthesized initializers. Bah! So the ModelNotCreated struct now has an initializer.

v0.2.0

01 May 18:42
Compare
Choose a tag to compare

Specializations

Create custom error handlers for converting specific errors to specific responses.

https://github.com/skelpo/APIErrorMiddleware#specializations

v0.1.0

20 Apr 20:10
Compare
Choose a tag to compare

Initial Release

Nothing changed much since the last release. Unless you consider existing a change from not existing. Then, yes, there was a big change.

Anyway, checkout the README to see what what the package even does!