Gil Neto

Sorry for the late reply. Here's the test itself: ``` test('delete an account', async () => { await mounted.setState({ activeAccount: { id: 'test', }, }); await mounted.instance().forceUpdate(); mounted.update(); expect(mounted.instance().state.activeAccount).toEqual({ id:...

@sstern6 no, `wrapper.debug()` (or, in my case, `mounted.debug()`) returns the component rendered properly, but only for the initial state. After the state update, the component remains the same (without properly...

@minznerjosh I know, that part of the code came from one of my desperate iterations 😛. I also tried having the remaining code as part of the callback for `setState`,...

@sstern6 this is the `findByAttr` implementation: ``` export const findByAttr = (wrapper, val) => wrapper.find(`[enzyme-attr='${val}']`); ``` I don't think shallow is usable here, because the component I'm testing is wrapped...

Let me try to be clearer, then. On the [AWS documentation](https://aws.amazon.com/blogs/compute/support-for-multi-value-parameters-in-amazon-api-gateway/), it states that when you pass repeated query string values, the object sent to Dynamo gets a specific field...

Any update? I'm also looking into the clustering capabilities and I'm feeling tempted to migrate.

The only downside I got aware of is the lack of Typescript support.