Kevin Stich
Kevin Stich
We use the `smithy-jsonschema` library as the basis for conversion to OpenAPI (`smithy-openapi`) and to generate CloudFormation Resource Schemas (`smithy-aws-cloudformation`). We don't currently offer a straight-to-JSON Schema build output, mostly...
Only the process of defining the trait in a model is outlined, [that's done so here in the spec](https://awslabs.github.io/smithy/1.0/spec/core/model.html#defining-traits). We'd gladly review anything you capture during your development as we...
You're right that the `offset` parameter to `SmithyPattern.Segment.parse` isn't used. I think the documentation for the parameter is a little misleading, causing your interpretation that it should always be given...
This was resolved in #1762 , running all plugins for a projection before failure.
I think any implementation of this should come after a solution to adding shapes directly to a service, akin to #1061 .
Closed by #1365
We haven't validated that an operation-level trait is the correct path forward for modeling if an operation can have a presigned url generated _or_ how this would need to interact...
It looks like this URI scheme is mixing a RESTful path with labels and then using the `:` to denote the RPC operation to perform on that resource. We don't...
It appears there are also checkstyle validations that are failing the build.
Resolving in favor of #2288