8000 Enum values that ignore naming conventions in Payment Handler API · Issue #418 · w3c/payment-handler · GitHub
[go: up one dir, main page]

Skip to content

Enum values that ignore naming conventions in Payment Handler API #418

@dontcallmedom-bot

Description

@dontcallmedom-bot

While crawling Payment Handler API, the following enum values were found to ignore naming conventions (lower case, hyphen separated words):

  • The value "shippingAddress" of the enum PaymentDelegation does not match the expected conventions (lower case, hyphen separated words)
  • The value "payerName" of the enum PaymentDelegation does not match the expected conventions (lower case, hyphen separated words)
  • The value "payerPhone" of the enum PaymentDelegation does not match the expected conventions (lower case, hyphen separated words)
  • The value "payerEmail" of the enum PaymentDelegation does not match the expected conventions (lower case, hyphen separated words)

See Use casing rules consistent with existing APIs in Web Platform Design Principles document for guidance.

This issue was detected and reported semi-automatically by Strudy based on data collected in webref.

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

      0