Skip to content

Support for ChromeDriver arguments #191

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

Merged
merged 3 commits into from
May 17, 2017

Conversation

michelkaporin
Copy link
Contributor

Added capability of providing ChromeDriver arguments. This resolves #189.

Copy link
Collaborator

@kevinsawicki kevinsawicki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left one very minor comment, thanks for adding support for this 👍

@@ -144,6 +146,10 @@ Application.prototype.createClient = function () {
args.push('spectron-env-' + name + '=' + self.env[name])
}

for (var index in self.chromeDriverArgs) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might be a little cleaner written in the style of line 141:

self.chromeDriverArgs.forEach(function (arg) {
  args.push(arg)
})

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated it 👍

README.md Outdated
See [here](https://sites.google.com/a/chromium.org/chromedriver/capabilities)
for details on the Chrome arguments.
* `args` - Array of arguments to pass to the Electron application.
* `chromeDriverArgs` - Array of arguments to pass to the ChromeDriver.
Copy link
Collaborator

@kevinsawicki kevinsawicki May 16, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this can be just to ChromeDriver instead of to the ChromeDriver.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

@michelkaporin
Copy link
Contributor Author

@kevinsawicki thanks, I forgot to add typings initially -> added them in 694288e now.

@kevinsawicki kevinsawicki merged commit 167a987 into electron-userland:master May 17, 2017
@kevinsawicki
Copy link
Collaborator

@michelkaporin thanks for this, great work 👍

I've published this in 3.7.1. The 3.7.x line supports Electron 1.7.x, so if you need this in Electron 1.6.x, let me know and we can merge this into that release line and cut a new 3.6.x spectron release.

@michelkaporin
Copy link
Contributor Author

@kevinsawicki it would be great if you can cut a new 3.6.x spectron release please, as we are on Electron 1.6.6 currently.

@kevinsawicki
Copy link
Collaborator

it would be great if you can cut a new 3.6.x spectron release please, as we are on Electron 1.6.6 currently.

Sure thing, published as 3.6.4 via #195

@michelkaporin
Copy link
Contributor Author

Perfect, thank you @kevinsawicki!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Passing --user-data-dir is interpreted as Spectron, not Chrome argument
2 participants