[BUG] Import does not work after clicking on Erase All

[Wizardbacon13]

Pre-submission Checklist

• I have searched existing issues to make sure this is not a duplicate
• I have cleared my browser cache and confirmed the issue persists
• I have checked this issue affects the latest version of the extension
• I have disabled other extensions to ensure this isn't a conflict issue
• I have included all the information requested below

Bug Description

The import/export will work if you don't mess with "Erase All" button, however when you click on the "Erase All" button, and then try to import a schedule, it will not update, the way to get around this is to import a second schedule, from a second .json schedule file, then use the original .json schedule file to revert back.

Steps To Reproduce

If you want to recreate the bug I encountered, use any 2+ different .json schedule files, or if you want to use the ones I used to recreate the bug, download my .json schedule files, "1.json" and "2.json", reload your build from chome://extensions, then go to the UTRP settings page and click the buttons in this order:

1. "Import Schedule"
2. "1.json" (or any other .json schedule file)
3. "Erase All"
4. "I Understand"
5. "Import Schedule"
6. "1.json" (using the same .json schedule file)

If you have tried to import the same .json schedule again, UTRP will not update to the schedule of that file, but then if you import "2.json" (or any other .json schedule file), then it updates to that file's classes, which then you can import 1.json (your original file) back,

Expected Behavior

I expect to be able to import my .json files, even after I clicked the "Erase All" button from the "Reset All Data" section.

Current Behavior

Instead, UTRP doesn't update from my imported .json files, after I clicked the "Erase All" button from the "Reset All Data" section.

Screenshots

2024-11-22.23-18-24.mp4

Debug Information

• UTRP Extension Version: [2.0.2.0]
• Browser Info: [130.0.6723.58 (Official Build) (64-bit)]
• OS: [Debian GNU/Linux 12 (bookworm) x86_64]

Console Logs

No relevant error messages

Additional Context

The bug seems to be related to how the code to reset data works.