chore: preserve original resolve
when decoding WIT package twice
#2125
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.
The second call to
wit_component::decode
reused theresolve
identifier from the first decode. This silently overwrites the originalresolve
, which can be misleading — especially since bothresolve
andresolve2
are referenced later in the function.I’ve updated the second match arm to bind to
resolve2
instead, so both decoded values are preserved independently as originally intended.This should clarify the logic and avoid unintentional data loss.