Power menu widget order scrambled

[nikander100]

Windows version

Windows 11

Windows OS build

26200.7705 (25H2)

YASB version installed

1.8.8 x64

Describe the bug

Updated from 1.8.7 > 1.8.8
noticed switch form cerberus to pydantic in release notes commit bced970
due to that the power menu now being forced in an incorrect fixed order.

due to the change to that the power menu order is now forced to the order as set in:

yasb/src/core/validation/widgets/yasb/power_menu.py

Lines 11 to 20 in a2004cf

	class PowerMenuButtonsConfig(CustomBaseModel):
	lock: list[str] | None = None
	signout: list[str] | None = None
	sleep: list[str] | None = None
	restart: list[str]
	shutdown: list[str]
	cancel: list[str]
	hibernate: list[str] | None = None
	force_shutdown: list[str] | None = None
	force_restart: list[str] | None = None

which feels counterintuitive (not being able to have a specific button at a specific place in the menu)

see image for example:

commented out buttons are top screenshot.

      buttons:
        # lock: ["\uea75", "Lock"] #1
        # sleep: ["\u23fe","Sleep"] #3
        # signout: ["\udb80\udf43", "Sign out"] #2
        # shutdown: ["\uf011", "Shut Down"] #5
        # restart: ["\uead2", "Restart"] #4
        # hibernate: ["\uf28e", "Hibernate"] #7
        # cancel: ["\udb81\udf3a", "Cancel"] #6
        shutdown: ["", "Shut Down"] #4
        restart: ["", "Restart"] #3
        signout: ["\uDB80\uDF43", "Sign out"] #1
        hibernate: ["", "Hibernate"] #6
        sleep: ["⏾", "Sleep"] #2
        cancel: ["", "Cancel"] #5

Relevant log output

N/A

[github-actions]

Thank you for the detailed bug report, @nikander100!

You've correctly identified the issue - the migration from Cerberus to Pydantic in v1.8.8 has introduced a regression where the power menu button order is now being forced to match the field definition order in the PowerMenuButtonsConfig class, rather than respecting the order you define in your config.yaml.

This is indeed counterintuitive behavior, as users should be able to control the order of buttons in their configuration. The issue is that Pydantic models (by default) don't preserve the order of fields as they appear in the user's YAML configuration - they follow the order defined in the Python class.

Your report clearly shows the problem:

• Expected: buttons appear in the order defined in config.yaml
• Actual: buttons appear in the order defined in the validation model (lock, signout, sleep, restart, shutdown, cancel, hibernate, force_shutdown, force_restart)

This will need to be reviewed by the maintainer to determine the best approach to preserve user-defined button ordering while still using Pydantic for validation.

---

YASB Support Bot

AI generated by YASB Issue Triage Agent

[amnweb]

It should be fixed in the dev release https://github.com/amnweb/yasb/releases/tag/dev