Extend the API with new methods · Teamwork/node-auto-launch#128

(0 Kommentare) (0 Reaktionen) (0 zugewiesene Personen)CoffeeScript (911 Stars) (111 Forks)batch import

enhancementhelp wanted

Beschreibung

Since we are support specifically the "hidden" argument, and because we support adding extra arguments (whatever please the developers), we could extend the API to provide a way to get some values.

Would proposing the following methods make sense:

openAsHidden() which would return a boolean telling wheteher the app is set to be launched as hidden/in background. It could mimic the method proposed by electron and extend it to all supported platforms.
- See https://github.com/Teamwork/node-auto-launch/issues/58 for a usecase
- Should we care if it was launched at login or system wide (if we ever support this option)?
getArguments() (or getExtraArguments()) would return an array of all the arguments sent to the app at autolaunch.
toggle() to take care of the logic to enable ou disable autolaunch
- https://github.com/Teamwork/node-auto-launch/pull/121
extend disable() method to remove enabled/disabled state in Windows registry.
- usecase: https://github.com/Teamwork/node-auto-launch/issues/22

Contributor Guide

Tech Stack: nodejs
Domain: apideveloper experience
Issue Type: feature
Schwierigkeit: 3
Geschätzte Zeit: 1-2 days
Aktivitätsstatus: fresh
Klarheit: mostly clear
Voraussetzungen: Basic Node.js knowledgeFamiliarity with auto launch concepts
Einsteigerfreundlichkeit: 45
Research-Richtung: Review existing API methods in the codebase to understand current structure. Investigate linked issues #58 (for openAsHidden use case) and #22 (for disable registry cleanup). Examine the toggle implementation in PR #121. Discuss with maintainers the questions raised about cross platform behavior and whether openAsHidden should differentiate between launch methods. Plan for adding getArguments() to return extra arguments. Ensure backward compatibility.