Fork me on GitHub

I'm building a version of aws-api for gcp. There's actually a nice openapi spec for the gcp api. Cognitect's aws-api merges parameters in all locations (headers, query string, path, & body) into a single map. Were there any cases where there was a clash (e.g., a param was named the same thing but located in a different place)? If so, how did you handle it?


For the GCP Compute API, this occurs 50 times. Curious about approaches on how to handle this.


How does the bring-your-own http client landscape of work look like? Have been thinking about the HTTP client in Java 11...


another thing: now that I say this out loud, I should try it out, but does aws-api survive graalvm native-image compilation?