docs: Update Check function examples with statecheck package implementations
#363
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Mentioned in a recent GH issue, our docs still reference the
Checkfunction in all the existing "best practice" examples.I went through and just adjusted them to match the current recommendation to use the
statecheckpackage. I omitted the custom state check implementations, mostly because some can be replaced by upcoming functionality in #330, but also because we should probably rewrite a good chunk of this documentation.This is just to point provider developers in the general direction of
statecheckbefore we deprecate theCheckfunction.