While working through some of the framework server refactoring as part of #215, it was necessary to extract some of the tfsdk.Attribute, tfsdk.Block, and tfsdk.Schema unexported methods into temporary functions within the internal/fwserver package so they did not become part of the public tfsdk APIs. For example, SchemaValidate() and SchemaModifyPlan(). This highlighted that a larger portion of the schema handling would benefit as being in internal packages and colocated again, rather than splitting the logic across packages, while still exporting provider developer functionality only as necessary in tfsdk or some other "public" package.
To be written up, but a current thought is that there should be an internal/schema or similar package which contains the full framework schema/attribute/block handling, while tfsdk or another package merely exposes anything that should be in the public API.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4