Dries Vints

Caching

3

Performing GraphQL calls can be costly and take quite a bit of time. Ideally I'd like to have dedicated caching support in the library. Most calls to check for sponsorships...

Leverage the newly added `cancelSponsorship` mutation: https://docs.github.com/en/graphql/reference/mutations#cancelsponsorship

Sync sponsorships with GitHub webhooks

2

It would be cool if we could sync incoming GitHub webhooks into a database table so sponsorships can be checked against a persistent storage instead of performing GraphQL API calls....

Fake GraphQL requests with HTTP client

1

To speed things up we should fake the GraphQL requests. This will also be necessary to allow pull requests from GitHub since those won't be authenticated with a token and...

Ideally we'd build a dedicated documentation website with separate PHP-only and Laravel sections so it's more clear how to use the library in specific situations.

With this library it should be possible to check if users are sponsoring through specific tiers. This will allow for even more fine-graned ACL capabilities and perk-granting. The API would...

For our Sponsorable trait we offer to set a GitHub username and token on the implementing class. But we don't actually check if the user or the token belong together....

Ideally we'd ship with a migration to add the `github` and `github_token` columns to the `users` table for Laravel. Make use of the same way of ignoring migrations in Laravel...

Extend the API with even more useful methods: ```php // Check if driesvints has a sponsor listing... $client->hasSponsorsListing('driesvints'); // Check if driesvints can sponsor nunomaduro... $client->canSponsor('driesvints', 'nunomaduro'); // Check if...

It'd be cool if the library could track sponsored amounts of users. This could enable new ways to grant users perks based on how much someone has sponsored already.