Skip to content

chore(cspell): add PISP and SECP terms to custom words - #379

Open
baaakgun4543 wants to merge 1 commit into
google-agentic-commerce:mainfrom
baaakgun4543:chore/cspell-pisp-secp
Open

baaakgun4543 wants to merge 1 commit into
google-agentic-commerce:mainfrom
baaakgun4543:chore/cspell-pisp-secp

Conversation

@baaakgun4543

Copy link
Copy Markdown

Description

constraints.py and constraints_tests.py use the PISP identifiers (payment initiation service provider: AllowedPisps, closed_mandate.pisp, ...) and the SECP256R1 curve name. None of these words is in .cspell/custom-words.txt. Because the spellcheck workflow checks every word in any changed file, a PR that touches either file fails spellcheck even when it adds no new words. This currently happens on #377 and #378.

This adds the exact forms reported by cspell, since the config is case-sensitive: otherpisp, PISP, Pisp, pisp, Pisps, SECP. They are inserted in the file's existing near-alphabetical order. No code changes.

  • Follow the CONTRIBUTING Guide.
  • Make your Pull Request title in the https://www.conventionalcommits.org/ specification.
  • Ensure the tests and linter pass (dictionary-only change).
  • Appropriate docs were updated (if necessary): not applicable.

constraints.py and its tests use PISP (payment initiation service provider) identifiers and the SECP256R1 curve name. They are not in the dictionary, so any PR touching those files fails the incremental spellcheck.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant