Skip to content

validate: suggest the intended field on unknown-key errors in claim PRs #12

Description

@davidpesce

Two authors have now had claim PRs fail on hand-authored field details (camp-index#82/#83 used security for security-contact; camp-index#62's author asked for docs before attempting). The schema rejects unknown properties, which is correct, but the error ('Additional properties are not allowed') gives no hint toward the intended key.

Proposal: when validation hits an unknown property, emit a did-you-mean suggestion against the schema's property names (difflib.get_close_matches is enough), and for the common claim case add one line pointing at AUTHORS.md Step 1's claim checklist (maintainers, security-contact, labels, tier: 1). Small change in validate.py plus a test.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions