added-rescan-progress-issue-744#894
Conversation
|
Nice @18c83fd3-25ea-4ed9-8205-2abeff9b3883! Really looks cleaner than the first PR. Thanks! Two things come to mind:
|
|
Added a flag isRescanProgressApiSupported to track if the API is supported |
🙏 🚀 What are those additional |
|
Utility scripts I made changes with and forgot to clean up after myself. DELETED Should be good to go now. |
src/context/ServiceInfoContext.tsx
Outdated
| // Initialize rescanProgress to undefined to avoid briefly showing old progress | ||
| dispatchServiceInfo({ | ||
| rescanProgress: undefined, | ||
| }) |
There was a problem hiding this comment.
Not here actually.. but before you schedule with setInterval, no?
|
improve error handling in the ServiceInfoContext.tsx file:
|
src/context/ServiceInfoContext.tsx
Outdated
| offer_list: Offer[] | null | ||
| nickname: string | null | ||
| rescanning: boolean | ||
| rescan_progress?: number |
There was a problem hiding this comment.
Last things before we can merge.. /session response does not contain a rescan_progress property. Please remove it.
(This causes the scanning text to flicker as the /session call updates it to undefined and the /getrescaninfo updates to the actual progress number)
Other than that, I think it is ready to be merged.
|
done. thanks for the feedback |
How are you so freaking fast? Amazing. |
theborakompanioni
left a comment
There was a problem hiding this comment.
Thanks @18c83fd3-25ea-4ed9-8205-2abeff9b3883.
Wonderful job! 🙏 🧡
Resolves #744.
cleaner fix