Daniel Bartholomae
Daniel Bartholomae
Hmm, this would still leave me with an inconsistent state. I could set a flag on the record that states whether the file is already confirmed or not. Sounds like...
I took the `this` pattern from [environments](https://jestjs.io/docs/en/configuration.html#testenvironment-string). It seemed a bit odd to me, too, but would be consistent. If the object needs to be serializable, then unfortunately a lot...
It should? Interesting, I'll give it another try. Last time I didn't get it to work. Basically what this feature proposal is about is providing a sanctioned way to do...
Just came here to leave the exact same suggestion and happy to see someone had the same idea before. To add a bit more flesh on why this would be...
I'll add a couple (and in doing so already found a typing error) soon.
Might be helpful to look at #1228 and implement this as a specialisation of `renameKeyWith` instead.
@vicary You might want to take a look at https://github.com/dbartholomae/lambda-middleware which I created out of a discussion around how to better use TypeScript types in middy. It attacks the problem...
It's not a replacement for the current functionality. I agree that there are many situations where the full spectrum is needed. But there might also be those where a slimmed...
We've worked more on our codebase and came to the realization that for us it is fine to always use errors instead of books and for type checking, so from...
Here's a thumbs-up from me - I might even be able to cook up a pull request for this if interested :)