Releases: ezypeeze/nuxt-neo
Releases · ezypeeze/nuxt-neo
v5.0.1
v5.0.0
5.0.0 (2022-03-12)
⚠ BREAKING CHANGES
- Parsing of params in route paths now uses the path-to-regexp library which is what express.js uses also. Before this change there was no validation of passed path params while now the API call will fail if the params don't match what the route path expects.
Bug Fixes
v4.3.1
v4.3.0
v4.2.1
v4.2.0
v4.1.0
Bug Fixes
- issue #10: Promise.catch() in plugins.api.template.js (2b7f053), closes #10
- fix middleware handler not being sequencially ran
Refactor
- add action middleware into Controller.ROUTES[middleware].middleware (deprecated from old way Controller.MIDDLEWARE) - controller middleware remains the same
Other
- upgrade dependencies for latest and stable available
v4.0.0 - Major Release
Features
- error handler: pass entire context nuxt object instead of only the error nuxt handler (ce0f598)
BREAKING CHANGES
- error handler: errorHandler will only have one parameter (of type Error) with the err.ctx object monkey-patched
v3.0.0 - Major Release
Feature
- support both client and server side success and error handlers
- add nuxt error page function resolver as errorHandler parameter
- add http error classes both on server and client side
Bug Fixes
- convert camelCase controller file name to dash case (for route url's endpoint)
Other
- upgrade devDependencies (including nuxt)
BREAKING CHANGES
- responseMiddleware is now called successHandler (successHandler function was removed) (used both on client and server side)
- errorHandler is now a string (file path), instead of a function (used both on client and server side)
- successResponse was renamed to serverSuccessResponse
- errorResponse was renamed to serverErrorResponse
- notFoundRouteResponse was renamed to serverNotFoundRouteResponse