-
Notifications
You must be signed in to change notification settings - Fork 113
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
Why the name I pass to AutoLaunch constructor is not be used? #92
Comments
In fixOpts, I comment out part of the code. AutoLaunch.prototype.fixOpts = function() { I just wonder if this is OK or not. |
I noticed the same thing... Without changing anything in the package's code (it obviously is a flaw that needs to be addressed, but the package doesn't currently seem actively maintained...), you can just overwrite the value after initialisation: AutoLauncher.opts.appName = 'YourAppName' |
Please see that we're looking for contributors / maintainers: #64. I'm happy to give access to people who are willing to help improve things, merge pull-requests, close issues, etc. |
Partially fixed in upcoming 6.0.0-rc.2. However, still used under macOS and I think I understand what was the purpose of this "clean up". It is not so much a clean up, but a fix when needed for some scenarios. It should have been documented and better applied per OS. Other improvements to come. |
node -v
):In your code in the AutoLaunch function,
you call this.fixOpts();
After this function, the name we pass will become another value.
In the fixOpts, I find author changes the this.opts.appName.
But I don't know why to do this.
If I comment out these code, then the name written in Registry will be what I pass.
The text was updated successfully, but these errors were encountered: