terraform-plugin-framework
terraform-plugin-framework copied to clipboard
Consider changing attr.Value implementations in types package to have Value in their name
It's very confusing to have types.String that doesn't define an actual type constraint, and instead holds a value. Maybe types.StringValue is clearer?
I'm 👍 for this type of change -- I personally appreciate the pattern of {InterfaceTypeName} and {Concrete}{InterfaceTypeName} where possible.
We're discussing a different approach to this problem over in #447, which will introduce its own breaking changes, so I think it is best to track it there. 👍
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.