You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey I had a question about the naming of the config keys for setting the paths of the binaries for chrome and chromedriver.
If I want to set paths to both chrome and chromedriver, I can do something like this:
config :wallaby,
chromedriver: [
# This is the path to chromedriver binary
path: "path/to/chromedriver",
# And this is the path to the chrome binary
binary: "path/to/chrome"
]
While reading the docs, I first assumed that there was a mistake in the description, but then going to the code (eg here and here) I see that the above is the correct way to configure it. So, I was curious about the rational behind using path for chromedriver but binary from chrome, rather than something like chrome_path and chromedriver_path (as an example). Is there some intuition that I am missing about the names?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hey I had a question about the naming of the config keys for setting the paths of the binaries for chrome and chromedriver.
If I want to set paths to both chrome and chromedriver, I can do something like this:
While reading the docs, I first assumed that there was a mistake in the description, but then going to the code (eg here and here) I see that the above is the correct way to configure it. So, I was curious about the rational behind using
path
for chromedriver butbinary
from chrome, rather than something likechrome_path
andchromedriver_path
(as an example). Is there some intuition that I am missing about the names?Beta Was this translation helpful? Give feedback.
All reactions