Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
P
Patron
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 17
    • Issues 17
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 0
    • Merge Requests 0
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Soapbox
  • Patron
  • Issues
  • #9

Closed
Open
Opened Jul 01, 2020 by Alex Gleason@alexgleasonOwner

Maybe store `acct` with the User

Originally the User struct looked like this:

User:

  • acct
  • stripe_cus_id

And it served only to link these two data points. I became convinced it would be better to make the ap_id the unique identifier, so I switched out acct for ap_id.

Now I'm starting to regret it, because getting donor info about a user looks like this:

  • GET /api/patron/v1/accounts/https%3A%2F%2Fhyrule.world%2Fusers%2Flink

When ideally it could look like this:

  • GET /api/patron/v1/accounts/link@hyrule.world

But I still have mixed feelings. I think I want to store both in the database, but we'll have to be sure both are present.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: soapbox-pub/patron#9