Skip to content

[CON-2361] feat: add PayPal read connector#2937

Open
Jkarage wants to merge 3 commits into
jk-paypal-metadatafrom
jk-paypal-read
Open

[CON-2361] feat: add PayPal read connector#2937
Jkarage wants to merge 3 commits into
jk-paypal-metadatafrom
jk-paypal-read

Conversation

@Jkarage
Copy link
Copy Markdown
Contributor

@Jkarage Jkarage commented Apr 29, 2026

Conventions

Read more: https://ampersand.slab.com/posts/deep-connectors-guide-6x4fhxne#ht0ds-reviewer-checklist

  • Connector uses internal/components
  • Metadata uses V2 metadata format
  • Read supports pagination and incremental sync
  • Raw response is returned as is for READ & METADATA, no formatting or flattening is performed.
  • Write payloads should accept what ReadResults.Fields is returning. Any unnecessary nesting around the input is removed.
  • Provider errors are mapped if non-standard (errors with 200 response code are converted to 4XX)
  • Custom fields, if not human readable names, are resolved to readable names.
  • Unit tests cover read/write/metadata logic (placed in /tests/)
  • Appropriate object names are used. Objects need to be resources, not actions (jobs and not jobs.list).
  • Modules are only being added because:
    • They share the same authentication scheme
    • The same base URL cannot be used to make a proxy call to objects in all modules
    • Different base URLs (drive.google.com vs google.com)
    • Object name collisions (same object name exists in two or more modules)

Live Read Tests:
Screenshot 2026-04-29 at 17 21 28

@linear
Copy link
Copy Markdown

linear Bot commented Apr 29, 2026

@Jkarage Jkarage requested a review from eberle1080 April 29, 2026 14:36
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