Olivier Mélois
Olivier Mélois
From what I gather, Zinc is currently invoked by mill in a way that prevents the compilation cache to be shared across machines (the fact that mill doesn't expose any...
If a model is constructed programmatically using dynamic trait values (ie shape ids + nodes), it is not possible to query the value using the class-parameterised variant of `getShapesWithTrait`. This...
 Currently smithy maps can only take string shapes as keys. Considering the protocol-agnostic nature of smithy, this is somewhat arbitrary and prevents its usage...
When writing smithy specifications by hand, traits can be written by : 1. directly annotating the shape they're applied on, in an "inlined" fashion 2. using the `apply` keyword, potentially...
Could you provide precisions related to the values that should be valid at runtime, regarding `httpResponseCode` trait, in the AWS protocols that support it ? In particular, considering the following...
Attempt at addressing https://github.com/disneystreaming/weaver-test/issues/651 Just a quick POC to see whether something can be done.
Some users are getting confused because of libraries that print `getMessage`, which currently returns `null` for smithy4s-generated throwables, except if one of the fields is identified to be a message...
See original comment from Jakub here : https://github.com/disneystreaming/smithy4s/pull/1455#discussion_r1551666855 > suggestion: UI-wise I think we could improve upon these code snippets by splitting them in two, in addition we could use...
In https://github.com/disneystreaming/smithy4s/pull/1423, the version of protocol-compliance tests that aws-http4s is working against has been bumped to 1.45.0, and some tests are now failing. In order to avoid blocking the release...
@kubukoz was right (... for once 😉). During code-generation and by default, we re-order case class fields in order to improve the UX of the generated case classes : optional...