Skip to content

Language implementation spec #89

@lgalabru

Description

@lgalabru

When starting a new language, we want to follow the following structure:

  • Setup CI
    • Linting
    • Unit tests
    • End to end test using harness / interop
      -example directory, exposing one simple endpoint
  • README:
    • Title
    • Badges (language, code-coverage)
    • Repo layout
    • Basic snippet of code using charge intent
    • How to use the lib
    • How to use the example
    • Client compatibility matrix:
      • x402/exact,
      • x402/upto,
      • x402/batch-settlement,
      • mpp/charge/pull,
      • mpp/charge/push,
      • mpp/session,
      • mpp/subscription
    • Server compatibility matrix:
      • x402/exact,
      • x402/upto,
      • x402/batch-settlement,
      • mpp/charge/pull,
      • mpp/charge/push,
      • mpp/session,
      • mpp/subscription
    • Coding convention / skill used for best practices (php best practices, etc)
    • Solana Dependencies
  • Source directory
    • Code coverage > 90%, reported
    • Methods/classes/structs documented for LSP / IDE auto-completion

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions