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
🎃 Hacktoberfest: Extend Developer Toolkit Web Browsing
🌐 Support Multiple Browser Engines (Chromium, Firefox, WebKit)
📝 Description
The Developer toolkit currently supports web browsing via the fetch_web_content method, but it's limited to Chromium. We need to expand this to support Firefox and WebKit for improved versatility and compatibility.
🎯 Objective
Enhance fetch_web_content to allow users to choose between Chromium, Firefox, and WebKit for web content fetching.
🛠️ Implementation Steps
Update fetch_web_content to accept a browser option
Implement browser selection logic using Playwright
Add error handling for unsupported browser options
We welcome contributions of all levels. If you have questions, please ask in the comments!
The text was updated successfully, but these errors were encountered:
blackgirlbytes
changed the title
Hacktoberfest: Extend web browsing in the developer toolkit to support multiple browser engines beyond Chromium (e.g., Firefox, WebKit)
🎃 Hacktoberfest: Extend web browsing in the developer toolkit to support multiple browser engines beyond Chromium (e.g., Firefox, WebKit)
Oct 19, 2024
🎃 Hacktoberfest: Extend Developer Toolkit Web Browsing
🌐 Support Multiple Browser Engines (Chromium, Firefox, WebKit)
📝 Description
The Developer toolkit currently supports web browsing via the
fetch_web_content
method, but it's limited to Chromium. We need to expand this to support Firefox and WebKit for improved versatility and compatibility.🎯 Objective
Enhance
fetch_web_content
to allow users to choose between Chromium, Firefox, and WebKit for web content fetching.🛠️ Implementation Steps
fetch_web_content
to accept a browser option✨ Key Features
🚀 Getting Started
fetch_web_content
in the Developer toolkit💻 Running Locally
Prerequisites
Setup
uv
uv
in your local Goose directory to set up the virtualenv and install dependenciesDevelopment Commands
uv run goose session start
uv run pytest tests -m "not integration"
orjust test
alias goosedev=\
uv run which goose``📚 Example Usage
After implementation:
🧪 Testing Checklist
📘 Documentation Updates
We welcome contributions of all levels. If you have questions, please ask in the comments!
The text was updated successfully, but these errors were encountered: