Brendan Hay

@magthe If you're using the generated (legacy) lenses, the usage for your example is intended to be: ```haskell import Amazonka.SQS ( newDeleteMessageBatch, newDeleteMessageBatchRequestEntry, newReceiveMessage, ) import Amazonka.SQS.Lens ( deleteMessageBatch_entries, receiveMessageResponse_httpStatus,...

This is helpful feedback, @magthe, thanks! The documentation for much of the work that has come along with 2.0 still needs improvement, and feedback like this lets us know what...

Hmm. This is a tough one and the exact use case (changing of the request per retry action) hasn't come up before. I'm going to write a small test project...

@gwils I'm fully booked trying to get a large `amazonka` release out. Once that's done I'll do the gogol one.

I'm in the process of porting all the `amazonka` build, CI, and generator changes to `gogol`, now that the former's 2.0 release is ready - which will pave the way...

As mentioned in the opening - treat this as documentation of exploratory work. There is no intention to push a particular approach within any foreseeable release window(s). > 1. The...

An approach to supporting synonyms could be to retain the existing smart constructors and CPP 🥴 everything up the wazoo: ```cabal flag NoFieldSelectors description: If the NoFieldSelectors extension should be...

This probably deserves a longer form reply, but to answer your question directly - there is no currently public roadmap for maintaining and improving `amazonka` and `gogol`. I have fairly...

The shake work mentioned is separate from the Nix/Bazel work. It's related to having a generator that is fully incremental (ie. only regenerate what has changed - which makes it...

A hesitant guess here is the private certificate in `"private_key"` for your `ServiceAccount` is failing to parse, but due to `Parser` instances and non-cumulative/monoidal errors it's simply showing the latter...