Skip to content

Conversation

@vardhan30016
Copy link

This PR fixes Issue #4506, where the default close behavior was not reflected
in the GUI when the setting onAppCloseKey was not set.

Root cause

closeJob was read from settings but not given a default when missing.

Fix

  • When closeJob is null or empty, enforce the default action "ask".
  • Immediately update the provider state so UI and behavior match.

Result

Multipass GUI now behaves correctly when first installed or when the user has
no stored preference.

Fixes #4506

@vardhan30016

When onAppCloseKey has no stored preference, Multipass would show incorrect
default behavior. This patch enforces the default 'ask' behavior when the
preference is empty or missing.

Signed-off-by: vardhan30016 <vardhannaidu17@gmail.com>
@vardhan30016
Copy link
Author

Thanks for the update! Yes, this PR is still in progress — currently waiting for a maintainer review and approval.
All checks have passed except the ones that require maintainer approval to run, which is expected for contributors without write access.

Once a maintainer reviews and approves the workflow, the remaining checks will run and the PR can move forward toward merging.

Let me know if anything else is needed from my side! 🙌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[GUI] Default behavior on close not reflected in settings

1 participant