Today we just passed 200 stars!!! :)
has anybody ever had a
Cannot destructure propertyhttpContentNegotiationof 'undefined' or 'null' error?
import middy from 'middy'
const {
httpContentNegotiation,
httpErrorHandler
} = middy.middlewares
const lovelyStuff = event => {
// do stuff
}
const handler = middy(lovelyStuff)
.use(httpContentNegotiation({ availableMediaTypes: ['application/json'] }))
.use(jsonBodyParser())
.use(httpErrorHandler())
export { handler }
I think it's because I'm using imports
this bumps up my file size from less than 1MB to 3.5MB
looking into your issue right now
have closed it, will investigate further
I have now realised that actually just editing the validator to pass the errors through as a string
rather than using
'Event object failed validation' would be possibly safer
have replied to your comments, thanks @lmammino ! middyjs/middy#155
In one of my middlewares I have a promise that needs to return before it can continue
however, if I add async/await to the function, I get a whole load of errors and pain
Iām returning a promise to a variable set in the middleware
I don't do any async/await in the middleware
but then I await it when I use it later on
HELP! Love Middy so far. Having an issue with writing jest tests with my custom middleware written with async/await. My middleware has a proper try/catch around the await. I've looked at the
ssm middleware that is part of the core for ideas. My middleware works fine when I remove that single async call to S3. But with it I keep getting UnhandledPromiseRejectionWarning
Is there some special way to implement a middleware that uses async/await
@lmammino Would love if you have a moment to chime in on this. middyjs/middy#270 Seems like a current limitation when trying to test custom middleware.
If anyone is in Calgary, be sure to hit me up.
Does anybody know how to assign error message for validation on input schema object?
Hey all! Is there any preferred way of reusing a configured set of middlewares?
I have a handler configured:
const handler = middy(async (event, context, callback) => {
(...)
callback(null, { });
});
handler.use(middleware1())
handler.use(middleware2())
handler.use(middleware3())
handler.use(middleware4())
module.exports = { handler };I'm looking for a good way of only having to specify something like:
const handler = withMiddlewares(async (event, context, callback) => {
(...)
callback(null, { });
});
module.exports = { handler };Where the handler is pre-configured with a bunch of middlewares.
I'm trying to avoid duplicating a bunch of handler configurations that are all going to be the same / similar.
Cheers!