Repository navigation
Fix webhook JSON example and add visible signup labels - #353
Merged
ralyodio merged 1 commit intoOct 11, 2026
Merged
Conversation
Contributor
Author
|
Thanks for merging! Does this report and fix qualify for your $2 CrawlProof feedback bounty? Update: I submitted the work to the ugig bounty as |
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.
The webhook Body example used
| nullunions that made it invalid JSON. Use concrete values in the example and explain nullable fields separately. Add persistent Email and Password labels associated with the signup inputs.Validation: JSON.parse and source checks for visible label/input associations pass (all failed before the change); git diff --check and tsc --noEmit pass. Installed dependencies with Bun 1.4.2 using the frozen lockfile and disabled install scripts/browser downloads. Full vitest run: 2743 passed, 18 failed, 9 skipped. All 18 failures also reproduce in the unchanged base commit across the same 9 files (ffmpeg availability and environment-sensitive behavior on Windows). No dependency or lockfile changes. Browser rendering was not exercised.
Implemented with AI assistance; no authenticated flows were exercised.
I found these while reviewing the four public pages (landing, pricing, signup, and webhook docs) for the CrawlProof $2 feedback offer. Does this public report/PR qualify, or is submission through ugig required? No reward approval is assumed. Regarding “Would you pay for this?”: not for our current project; we do not currently need recurring site audits, and only public flows were evaluated.