endgame
endgame
Example: Every value in `apigateway`'s `CacheClusterSize` type contains only numbers and dots, so they all get mashed together into a single strange pattern: https://github.com/boto/botocore/blob/ac9ce8eb9ab4296608c95c5d04461266925d90e2/botocore/data/apigateway/2015-07-09/service-2.json#L2337-L2350 Affected types include: * `amazonka-apigateway`: `CacheClusterSize`...
These new files in botocore: https://github.com/boto/botocore/commit/16e66a19f878f601334d4a3711132a1322b549fc This would allow us to make requests to the FIPS-compliant and/or dual-stack endpoints. Not sure exactly how this will work, but writing it down...
Currently `lib/amazonka-core/src/Amazonka/Endpoint.hs` hardcodes endpoints for STS; we probably want a boolean flag somewhere to toggle this (maybe like the `s3AddressingStyle` field in `Service`?).
The `sts:AssumeRole` call can take a `SerialNumber` and `TokenCode` parameter, and `~/.aws/config` can take an `mfa_serial` field in its profiles. We should support this.
Rebuilding my take on the hierarchy hashed out at the end of the [comment thread](https://github.com/tomjaguarpaw/product-profunctors/pull/54#issuecomment-754205222) on #54 in a commit-by-commit branch Defines: * Profunctor => SemiproductProfunctor => ProductProfunctor This operates...
Once #64 goes in, we'll need to do a major bump. Let's deprecate things as promised (threatened?).
My take on the hierarchy hashed out at the end of the [comment thread](https://github.com/tomjaguarpaw/product-profunctors/pull/54#issuecomment-754205222) on #54. Given that breaking changes are necessary, this is fairly aggressive about breaking them to...
From [reddit](https://www.reddit.com/r/haskell/comments/v728gz/is_there_an_idiomatic_way_to_have_a_record_but/icijab8/), discussing `FRepresentable`, but this could exist for `Representable` also. My motivating thought was when you have a higher-kinded record with its fields indexed by a GADT, you can...
Maintain the ordering of status values in the haddocks