-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generated code doesn't compile when there's a smithy shape using a reserved name #1051
Comments
related: #389 |
Wanna have a go at fixing ? |
@Baccata yeah, will give it a go, any hint on the related code parts? |
not off the top of my head |
|
btw, what is the preferred solution here? to override the name (e.g. make it |
@miguel-vila, actually, I'll fix it. The "reservedNames" was there in the first iterations of smithy4s. In the last year, a much more robust mechanism was introduced by @yisraelU, so dropping the reserved "types" altogether is a better solution. |
Closing as the PRs fixing this have been merged. |
for example this smithy code:
generates this code which doesn't compile:
because it's referring to
_Set
instead ofSet
in the same packagereproduced at #1050
The text was updated successfully, but these errors were encountered: