Skip to content
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

Use the type name to help resolve name clashes #107

Merged
merged 1 commit into from
Feb 12, 2024
Merged

Conversation

Frassle
Copy link
Member

@Frassle Frassle commented Feb 10, 2024

Better conflict resolution for conflicting source names. They'll now use the objects type name to help build a unique name.

See #88

@@ -31,6 +31,16 @@
"type": 4,
"computed": true
}
},
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I needed another type with a different name to test this case.

inputOne = "Hello ${aThingResource.result}"
inputTwo = myaThing
})

resource "aThingAnotherResource" "simple:index:anotherResource" {
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note that before this would have just ended up being called "aThingResource2"

@Frassle Frassle force-pushed the fraser/renameViaType branch from 1999591 to ecff5cc Compare February 10, 2024 13:15
@Frassle Frassle force-pushed the fraser/renameViaType branch from ecff5cc to c8dd6db Compare February 10, 2024 17:32
@Frassle Frassle merged commit 51d619c into main Feb 12, 2024
5 checks passed
@Frassle Frassle deleted the fraser/renameViaType branch February 12, 2024 13:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants