Repository navigation
Fix scraping-stack composer.json; say GeeTest v3 in the v3 pack code - #3
Merged
Merged
Conversation
- articles/captchaai-scraping-stack-100-budget/php/composer.json: the "description" value had doubled quotes since fdd071f, so the file was not valid JSON and Composer could not read it. It now matches the pack's node/package.json description. It was the only invalid JSON file in the repo. - articles/how-to-solve-geetest-v3-using-api: the console hints and comments in all 10 language files said a bare "GeeTest" ("... or GeeTest initialization call.", "GeeTest verification endpoint.", "the 3 GeeTest values"); they now say "GeeTest v3". Strings and comments only: the API method (method=geetest), the response field names and all identifiers are unchanged. Co-Authored-By: Claude Opus 5.5 <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
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.
Two small fixes in one PR.
1.
captchaai-scraping-stack-100-budget/php/composer.jsonwas not valid JSONThe
descriptionvalue had doubled quotes (""Build a Full ... CaptchaAI" - CaptchaAI example") since fdd071f, sojson.loadand Composer both failed on it (Expecting ',' delimiter: line 3 column 22). It now readsBuild a Full Scraping Stack Under $100/Month Using CaptchaAI - CaptchaAI example, the same as the pack'snode/package.json. This was the only invalid JSON file in the repo (all other*.jsonfiles parse).2.
how-to-solve-geetest-v3-using-api: say "GeeTest v3" in the code tooCaptchaAI solves GeeTest v3 only. #2 relabelled the docs; the console hints and comments in the 10 language files still said a bare "GeeTest". Now (29 lines, 3 per file, 2 in Go):
... in the page source or GeeTest initialization call.->... GeeTest v3 initialization call.GeeTest verification endpoint.->GeeTest v3 verification endpoint.// ... the 3 GeeTest values->// ... the 3 GeeTest v3 values(not in Go, which has no such comment)Files:
bash/solve.sh,csharp/Solve.cs,go/solve.go,java/Solve.java,kotlin/solve.kt,node/solve.js,php/solve.php,python/solve.py,ruby/solve.rb,rust/src/main.rs.Not changed
method=geetest), the response field names (geetest_challenge,geetest_validate,geetest_seccode) and all identifiersChecked locally:
json.loadand PHPjson_decodeon the fixed composer.json,python -m py_compile,node --check,php -l,bash -n. The other languages are covered by the CI jobs on this PR.🤖 Generated with Claude Code