-
Notifications
You must be signed in to change notification settings - Fork 15.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Add data parameter to app.requestSingleInstanceLock()
#30891
feat: Add data parameter to app.requestSingleInstanceLock()
#30891
Conversation
e28a18d
to
aaeb805
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
API looks good to me.
This PR requires review from @electron/wg-upgrades |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just needs some doc cleanup.
patches/chromium/feat_add_data_parameter_to_processsingleton.patch
Outdated
Show resolved
Hide resolved
patches/chromium/feat_add_data_parameter_to_processsingleton.patch
Outdated
Show resolved
Hide resolved
patches/chromium/feat_add_data_parameter_to_processsingleton.patch
Outdated
Show resolved
Hide resolved
patches/chromium/feat_add_data_parameter_to_processsingleton.patch
Outdated
Show resolved
Hide resolved
patches/chromium/feat_add_data_parameter_to_processsingleton.patch
Outdated
Show resolved
Hide resolved
patches/chromium/feat_add_data_parameter_to_processsingleton.patch
Outdated
Show resolved
Hide resolved
patches/chromium/feat_add_data_parameter_to_processsingleton.patch
Outdated
Show resolved
Hide resolved
patches/chromium/feat_add_data_parameter_to_processsingleton.patch
Outdated
Show resolved
Hide resolved
patches/chromium/feat_add_data_parameter_to_processsingleton.patch
Outdated
Show resolved
Hide resolved
patches/chromium/feat_add_data_parameter_to_processsingleton.patch
Outdated
Show resolved
Hide resolved
@jkleinsc windows ci patch failure seems weird, I am unable to repro it locally. Any idea whats happening there ? |
62f1e14
to
0458026
Compare
API LGTM |
Merging as CI failures are flake unrelated to PR. |
Release Notes Persisted
|
I was unable to backport this PR to "15-x-y" cleanly; |
I have automatically backported this PR to "16-x-y", please check out #31444 |
…on#30891) * WIP * Use serialization * Rebase windows impl of new app requestSingleInstanceLock parameter * Fix test * Implement posix side * Add backwards compatibility test * Apply PR feedback Windows * Fix posix impl * Switch mac impl back to vector * Refactor Windows impl * Use vectors, inline make_span * Use blink converter * fix: ownership across sequences * Fix upstream merge from Chromium Co-authored-by: deepak1556 <hop2deep@gmail.com>
…on#30891) * WIP * Use serialization * Rebase windows impl of new app requestSingleInstanceLock parameter * Fix test * Implement posix side * Add backwards compatibility test * Apply PR feedback Windows * Fix posix impl * Switch mac impl back to vector * Refactor Windows impl * Use vectors, inline make_span * Use blink converter * fix: ownership across sequences * Fix upstream merge from Chromium Co-authored-by: deepak1556 <hop2deep@gmail.com>
…on#30891) * WIP * Use serialization * Rebase windows impl of new app requestSingleInstanceLock parameter * Fix test * Implement posix side * Add backwards compatibility test * Apply PR feedback Windows * Fix posix impl * Switch mac impl back to vector * Refactor Windows impl * Use vectors, inline make_span * Use blink converter * fix: ownership across sequences * Fix upstream merge from Chromium Co-authored-by: deepak1556 <hop2deep@gmail.com>
…on#30891) * WIP * Use serialization * Rebase windows impl of new app requestSingleInstanceLock parameter * Fix test * Implement posix side * Add backwards compatibility test * Apply PR feedback Windows * Fix posix impl * Switch mac impl back to vector * Refactor Windows impl * Use vectors, inline make_span * Use blink converter * fix: ownership across sequences * Fix upstream merge from Chromium Co-authored-by: deepak1556 <hop2deep@gmail.com>
…on#30891) * WIP * Use serialization * Rebase windows impl of new app requestSingleInstanceLock parameter * Fix test * Implement posix side * Add backwards compatibility test * Apply PR feedback Windows * Fix posix impl * Switch mac impl back to vector * Refactor Windows impl * Use vectors, inline make_span * Use blink converter * fix: ownership across sequences * Fix upstream merge from Chromium Co-authored-by: deepak1556 <hop2deep@gmail.com>
…on#30891) * WIP * Use serialization * Rebase windows impl of new app requestSingleInstanceLock parameter * Fix test * Implement posix side * Add backwards compatibility test * Apply PR feedback Windows * Fix posix impl * Switch mac impl back to vector * Refactor Windows impl * Use vectors, inline make_span * Use blink converter * fix: ownership across sequences * Fix upstream merge from Chromium Co-authored-by: deepak1556 <hop2deep@gmail.com>
Description of Change
Fixes #18434
Fixes #23220
Affects microsoft/vscode#97626
This PR adds a new parameter to
app.requestSingleInstanceLock()
which takes in a JSON object. When a second instance is started and calls that API with an object, the object will be sent from the second instance to the first instance.CC @deepak1556
Checklist
npm test
passesRelease Notes
Notes: add new data parameter to
app.requestSingleInstanceLock()