fix: codegen structure members more safely to avoid conflicts with package names #1444
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #
(none)
Description of changes
Presently, a structure member which shares a name with a top-level package cannot be codegenerated by smithy-kotlin. For example, if a structure
Foo
has a memberaws
and the service's fully-qualified package starts withaws.
the following code will be generated (heavily trimmed):Unfortunately, there's no way to unambiguously refer to a package name when its shadowed inside of a statement scope. Since the conflict does not exist at the file level, this PR solves the problem by capturing references to necessary builder objects in file-local variables and invoking those in DSL builder methods instead:
I don't love this and I'm open to alternative approaches.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.