Fetch Domain access
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start by locating ChromeDevToolsSession and checking how existing domain accessors are exposed. Investigate the Chrome DevTools Protocol Fetch domain and determine the expected getFetch() API; the work is done when Fetch access is available through ChromeDevToolsSession and its behavior is covered by the project's relevant tests.
Written by the indexing model from the issue text.
Description
I could not seem to find a way to get access to the Fetch Domain.
I think a ChromeDevToolsSession.getFetch() implementation is required; unless someone can tell me otherwise.
- Dominant language
- Java
- Stars
- 48
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from HubSpot/ChromeDevToolsClient
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 42/100
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
All issues in HubSpot/ChromeDevToolsClient
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
opensearch-project/k-NN#3597 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100