Support Linux development identity and deep links - #130
Draft
SRWieZ wants to merge 4 commits into
Draft
Conversation
Member
Author
|
CI note: the |
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.
What changed
Give Linux development apps a stable desktop identity and make custom protocol delivery reliable across cold and warm application starts.
StartupWMClassxdg-mimeopen-url, andsecond-instanceWhy
Linux shells resolve a running window identity through a desktop entry. The same entry is also the freedesktop integration point for development protocol handlers. Deep links can reach Electron before Laravel and its event endpoint are available, so immediate delivery can lose OAuth callbacks on cold start.
Production protocol declarations continue to use electron-builder. macOS and Windows use their existing registration mechanisms while sharing the queued delivery path.
Coexistence and DX
Development never reuses the production desktop ID. Its identity includes a
nativephp-devmarker and a checkout-path hash, so production builds and parallel checkouts remain separate. The development entry is hidden from launchers and refreshed atomically. Failure to write it or invokexdg-mimeemits a warning without preventing startup.Validation
resourceClassanddesktopFileNameRemaining manual validation