fix: π device selection after aborted flow #7778
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.
β Checklist
npx changeset
was attached.π Description
I'm opened to alternative solutions.
TLDR: I'm not completely satisfied with this solution but I don't see another way which doesn't involve a major refactor.
The issue comes from the current structure of
DeviceActionModal
which relies on thedevice
prop andresult
internal state to trigger the drawer. Onceresult
is set the drawer is not supposed to re-opened and sincedevice
is not necessary reset something like this doesn't always work:(also it might break some other flow unrelated to ledger sync).
The way I see it selecting a device should imperatively trigger the device interaction. But this component is used this way everywhere else there is a device interaction on LLM.
Screen.Recording.2024-09-09.at.13.23.50.mov
β Context
π§ Checklist for the PR Reviewers