Add blockTag
to observerId
to avoid id collisions
#2019
Merged
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.
While using
wagmi
I notice that both of myuseWatchBlocks
hooks provide latest blocks even though one was suppose to subscribe to finalized blocks.It seems there is
observerId
collision. Fix includesblockTag
in theobserverId
to make it unique.PR-Codex overview
This PR focuses on adding
blockTag
toobserverId
inwatchBlocks
to prevent id collisions.Detailed summary
blockTag
parameter towatchBlocks
functionobserverId
to includeblockTag
to avoid id collisions