error handling for semesters with no data

[Cattn]

EX: if I click on Summer 2026 right now, it errors without the ability to easily recover (due to me not having classes then obviously)

EDIT/TODO:

Add a back button to the processing courses page/popup

[miretskyd]

I noticed the same thing. I was thinking we could just implement a back button on the get calendar page.

This is probably something I could implement, but I doubt I'll be able to do it until next week. @Cattn , lmk if you're able to do it sooner.

[jaspermayone]

we could show a "no data" screen or smth with a back button?

[miretskyd]

@jaspermayone can you drop an svg I can use for the back button?

we could show a "no data" screen or smth with a back button?

For the "no data" screen, you mean like a separate Svelte page? If so then yeah I could write a new page.

[jaspermayone]

@jaspermayone can you drop an svg I can use for the back button?

we could show a "no data" screen or smth with a back button?

For the "no data" screen, you mean like a separate Svelte page? If so then yeah I could write a new page.

yea that works @miretskyd

[jaspermayone]

and i dont have an svg

[jaspermayone]

I think @Cattn uses an icon library here and theres def one in there

[miretskyd]

@jaspermayone @Cattn I thought of a much easier idea...what if we just disable the button for next_term when there is no data? Would that work you think?

[Cattn]

@jaspermayone material symbols, filter by rounded

https://icon-sets.iconify.design/

[Cattn]

That also works @miretskyd we should probably have both, just in case an error/issue occurs on the page, a back button isn't a bad idea

[miretskyd]

That also works @miretskyd we should probably have both, just in case an error/issue occurs on the page, a back button isn't a bad idea

@Cattn What kind of error/issue are you referring to? I'm not really sure having both would work because if the button is disabled correctly then there's no need for the separate page to display "no data". UI wise I personally think it looks nicer, and the user would probably know why the button is disabled so I don't really see an issue there.

Putting disabled={!$storedProcessedData.some((d) => String(d.termId) === terms?.next_term.id?.toString())} in the input seems to work perfectly fine. Lmk your thoughts.

[Cattn]

I think I misread what the back button was for. I meant that we should have a back button on the processing data/process data page. Because if the user ends up on that page w/ no data, they can't escape without reopening the extension.

[miretskyd]

I think I misread what the back button was for. I meant that we should have a back button on the processing data/process data page. Because if the user ends up on that page w/ no data, they can't escape without reopening the extension.

Right, so do we just want a back button on that page in general? Is that what you're saying?

[Cattn]

Yes

[miretskyd]

Ah ok, I'll just do that then with no separate page?

[Cattn]

I can do that, I'll just add it to the issue