Mike Nason

We use CDK and serverless framework. I've added stacks from both fine, but a few serverless framework ones are giving me this error.

> Dumb question probably: Why do you want trace_context to be stringified in the first place? Not a dumb question at all @tirumaraiselvan! We have an ingest endpoint set up...

> It's hard to give any concrete advice without knowing more about why you're consuming the whole `event` object this way. The `event` object has four possible fields: `op`, `data`,...

Small update: I have a slightly better fix than editing the `serverless-webpack` code in my node_modules: ```js const chmodr = require('chmodr') const { promisify } = require('util') class WebpackPermissionsFixPlugin {...

Hi @glebmikulko, you're right it has been a while. Unfortunately I have less time these days for this project, and my work has shifted me away from as much front...

Nice catch @mattlubner -- thanks for the detailed issue 🖖 You're right it is getting the entire `RSAA` now, so something like this should work: ```js payload: action => ({...

@mattlubner thanks for the clarification! Ah I see -- the meta properties on a REQUEST_TYPE action should be the resolved values, not the functions passed to this middleware to generate...

Hi @abimelex, The [Lifecycle](https://github.com/agraboso/redux-api-middleware#lifecycle) docs describe that errors at the request phase will dispatch a `REQUEST` action (in your case `types.API_POST_CREDENTIALS_REQUEST`) with an error payload. Can you confirm if that...

Hi @adam8810, that would be a welcome addition indeed. This is not possible today and we'd need to be able to provide a way for users to pass in their...

The [`fetch` spec](https://fetch.spec.whatwg.org/) does not mention "timeout" at all. See https://github.com/matthew-andrews/isomorphic-fetch/issues/48 for more context. I understand this "expected behavior" leaves a lot to be desired. We've added the ability to...