chore(webui): use consistent/correct year order for Wolf Hunt dropdown menu #2890

Closed
Animan8000 wants to merge 2 commits from Animan8000:wolfOrder into main
Contributor

Currently in the WebUI the year order of the Wolf Hunt dropdown menu is not consistent to other events that have a year dropdown menu. {2C761E0B-77FF-46CD-9CFF-923A86254FBE}.png

On Wolf Hunt it currently goes from oldest to latest, rather than the other way around. This PR fixes the small inconsistency while keeping the 2025 event the default one.

Currently in the WebUI the year order of the Wolf Hunt dropdown menu is not consistent to other events that have a year dropdown menu. <img width="432" alt="{2C761E0B-77FF-46CD-9CFF-923A86254FBE}.png" src="attachments/62ef6aeb-f019-4807-a788-53cd1bc7baa7"> On Wolf Hunt it currently goes from oldest to latest, rather than the other way around. This PR fixes the small inconsistency while keeping the 2025 event the default one.
Animan8000 added 2 commits 2025-10-11 11:50:30 -07:00
src/services/worldStateService.ts aktualisiert
All checks were successful
Build / build (pull_request) Successful in 1m40s
efa02dd40c
Owner

I agree, but let's keep the values meaning the same as they did before

I agree, but let's keep the values meaning the same as they did before
Author
Contributor

I agree, but let's keep the values meaning the same as they did before

That would activate Wolf 2019 as the default one (line 2366 & 2367), if you activate the event the first time in WebUI (while also not having a value present in config.json in advance yet). I intentionally swapped the values to keep the identical behavior (2025 being the default one like before), while also fixing the dropdown menu visually.

> I agree, but let's keep the values meaning the same as they did before That would activate Wolf 2019 as the default one (line 2366 & 2367), if you activate the event the first time in WebUI (while also not having a value present in config.json in advance yet). I intentionally swapped the values to keep the identical behavior (2025 being the default one like before), while also fixing the dropdown menu visually.
Owner

there's no 'default one', I just want you to revert worldStateService and also swap the value

this whole PR could've been Ctrl+Shift+Arrow Down

there's no 'default one', I just want you to revert worldStateService and also swap the value this whole PR could've been Ctrl+Shift+Arrow Down
Sainan closed this pull request 2025-10-11 12:06:12 -07:00
All checks were successful
Build / build (pull_request) Successful in 1m40s

Pull request closed

Sign in to join this conversation.
No description provided.