fix(provider): update examples to use ProviderBuilder
best practices
#43
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.
Motivation
Closes: #42
Blocked by: alloy-rs/alloy#436Solution
This solution comes with the recognition that for the time being we continue to iterate on the API, narrowing down to the best. Therefore the term best practice evolves over time, goal is to consistently show the best version of the API across the examples.
ReqwestProvider
to useProviderBuilder
on_ws
andon_ipc
methods on the builderPR Checklist