3 ms·

Thanks for pointing out the why not. > Our Smithy->Fern converter is in development so that Smithy users can take advantage of our SDK generators. This is a g

Thanks for pointing out the why not. > Our Smithy->Fern converter is in development so that Smithy users can take advantage of our SDK generators. This is a good thing although there's definitely not going to be lossless. Smithy trait seem to be an escape hatch for everything, I believe it could be used to achieve the same but maybe not easier. They already have pagination traits. And their http error is per operation, endpoint is also per operation, so I think the error is bound to operation as well (https://smithy.io/2.0/spec/http-bindings.html#httperror-trait https://smithy.io/2.0/spec/http-bindings.html#httperror-trai...)

zachkirsch 4y ago
> Smithy trait seem to be an escape hatch for everything, I believe it could be used to achieve the same but maybe not easier. No doubt! This is definitely part of our thinking - there's a lot of things that are _possible_ in Smithy (and OpenAPI), but it requires you to be an expert and really understand how things work. For 90% of the use cases, it should be dead simple. For the remaining 10%, it's okay to rely on more complex features like plugins and traits.