Schema complaiance incorrect field documentation #8
Labels
No labels
Compat/Breaking
Compat/Deprecation
Kind
Bug
Kind
Chore
Kind
Documentation
Kind
Enhancement
Kind
Feature
Kind
Investigation
Kind
Question
Kind
Security
Kind
Testing
Meta/Good First Issue
Meta/Help Wanted
Meta/Stale
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Status/Needs Triage
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
XeplosionGames/minecraft-provider-analysis#8
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Where is the problem?
schema/provider-schema-v2.3.json (provider.reviews.complies_with_guidelines and
compliance_notes descriptions), tools/capture-form/index.html (Reviews step
label), docs/capture-guide.md, docs/bootstrap-guide.md
Type of problem
Incorrect — the docs say something wrong
What's wrong and what should it say?
complies_with_guidelinesand its label/description were worded as generic"scraping guidelines" compliance. The field is actually specifically about
compliance with Trustpilot's Terms of Service (this is the reviews section —
trustpilot_url, review_count, scrapes are all Trustpilot-scoped).
Corrected wording has already been applied locally (not yet committed):
Terms of Service. Null = not yet assessed."
robots.txt kept as a secondary note
Deliberately NOT renamed: the JSON key
complies_with_guidelinesitself, thesheet column
Complies_With_Guidelines?, and the 115 existing provider filefield names are unchanged — only descriptions/labels were corrected, to avoid
a coordinated rename across the sheet, bootstrap.py, and all provider files.
If a full rename is wanted later, that's separate follow-up work.
Additional context
Ready as a PR — just needs committing. All 71 existing tests pass unmodified
since only description/label text changed, not field names or schema
validity rules.
Checklist
Docs Update templateto Schema complaiance incorrect field documentation