engine=amazon --all-pages silently adds `k=` (I am using node=)
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Start by reproducing engine=amazon --all-pages with node=xxx and inspect the resulting serpapi_pagination.next value. Trace how pagination parameters are built and forwarded; done means node= remains the pagination parameter and k= is not added unexpectedly.
Written by the indexing model from the issue text.
Description
I am using node=xxx (not k=xxx). Maybe the server is adding k= to serpapi_pagination.next, even when I am using node=?
- Dominant language
- Go
- Stars
- 13
- Forks
- 4
- 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 serpapi/serpapi-cli
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
serpapi/serpapi-cli#13 ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 55/100
serpapi/serpapi-cli#10 ·
-
serpapi/serpapi-cli#8 · 2 comments · 1 assignee ·
All issues in serpapi/serpapi-cli
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·