Skip to content

Commit 00e6cb1

Browse files
bendbennettbflad
andauthored
Update migration guide to indicate Set field and SchemaSetFunc equivalents are not required when using the Framework (#541)
* Adding documentation to indicate that Set field and associated SchemaSetFunc does not need to be migrated to the Framework (#540) * Apply suggestions from code review Co-authored-by: Brian Flad <[email protected]> Co-authored-by: Brian Flad <[email protected]>
1 parent bf1ce9b commit 00e6cb1

File tree

1 file changed

+2
-0
lines changed
  • website/docs/plugin/framework/migrating/schema

1 file changed

+2
-0
lines changed

website/docs/plugin/framework/migrating/schema/index.mdx

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -145,6 +145,8 @@ Remember the following differences between SDKv2 and the Framework when completi
145145
`tfsdk.Schema` structs instead.
146146
- In SDKv2, schema structs are returned when a provider, resource, or data type is created. In the Framework, the
147147
provider and each resource and data type have a `GetSchema` method that returns the schema.
148+
- In SDKv2, schema structs have a `Set` field which can be populated with a `SchemaSetFunc` which is used for hashing.
149+
In the Framework, this is not required and does not need to be migrated.
148150
- The `tfsdk.Schema` struct includes fields that you use to define
149151
[attributes](/plugin/framework/migrating/attributes-and-blocks/attribute-schema) and
150152
[blocks](/plugin/framework/migrating/attributes-and-blocks/blocks) for your provider and each resource

0 commit comments

Comments
 (0)