Repository navigation
Release v0.5.1 - #76
Merged
Merged
Conversation
Keep the app-library fallback available after shell API destruction. Add a lifecycle regression test for issue #75.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Correction
Omalaunch now keeps its application-library fallback available if Omarchy destroys the injected shell API while the menu remains loaded. This addresses the empty Apps list and missing application search results reported in #75.
The unused fallback enable switch has been removed. The host's shared library still takes priority. The fallback loads only when no shared library is available and a service source is set. Menu destruction still releases the fallback and its launch feedback.
Verification
Update
Restart the shell so the updated QML replaces the cached menu. Issue #75 remains open pending confirmation from the reporter.