Open daddykotex opened 1 year ago
I like the idea, but that will require protocol-specific handling in the codegen I think. It's probably not a huge problem though, IIRC the decline module does something similar, and so does smithy-playground.
I like the idea, but that will require protocol-specific handling in the codegen I think
I think I'm fine with it because it's not adding any protocol specific logic to the generated code
Title says it all but basically: it's not the first time I work in a project where the specification is pulled from somewhere by the build tool. Some code is generated from it and I am implementing the service, and I run it to test it. But sometimes I forget what's the path to reach the specific operation.
Would adding something like the following be interesting:
That would make it easier to figure out by using the IDE go-to-definition feature and ending up in the codegen where you find the info. You still don't have all the info, but sometimes that's all you need.