-
Notifications
You must be signed in to change notification settings - Fork 4
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
Test that map keys don't get renamed #101
Conversation
value = { | ||
CAPS = aResource.result | ||
camelCase = 1 | ||
snakeCase = 2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that these are still being renamed. Fixing this is a bit more involved. If we just flip the logic to assume things are maps not objects then we end up renaming a lot of { k: v}
expressions in TF source code which are then used for object values.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is probably fine that output objects are renamed because the type of these becomes are object type from component outputs, not a map.
Actually this probably fixes #53 as well. |
Sorry, I need to take care of #99 |
ba1a256
to
d1585ea
Compare
Tests are unblocked and should now pass with #105 |
d1585ea
to
6e7fcda
Compare
Fixes #100.
This doesn't fix every rename, there's still cases where we should be leaving keys as is but are renaming them.