Use WebDriver::managed in README and lib.rs example#306
Merged
stevepryde merged 1 commit intomainfrom Apr 30, 2026
Merged
Conversation
The crate's docs in the book and examples already lead with WebDriver::managed; the top-level README and crate-root rustdoc were still showing the chromedriver-on-a-port flow. Switch them over so the first thing a new reader sees matches the recommended path. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
README.mdsymlink) fromWebDriver::new("http://localhost:9515", caps)toWebDriver::managed(caps).WebDriver::managedthe reader no longer has to startchromedriveron a port — it auto-downloads, runs, and tears down for them.Why
The book, the in-tree examples, and the
WebDriver::managedrustdoc all already lead with the managed flow. The README and crate-root docs were the last surface still pointing newcomers at the manualchromedriver-on-a-port path, which made the recommended flow look optional. Now first impressions match the rest of the docs.Test plan
cargo doc --no-deps --all-features(intra-doc link toWebDriver::managedresolves cleanly)🤖 Generated with Claude Code