GitHub’s REST API was perfect. Now THIS is more perfect.
GitHub provides a well-known API that accepts a lot of traffic.
GitHub’s API is considered an industry-standard we would do well to emulate:
Use the https://developer.github.com/early-access/graphql/explorer/
Perform an introspection query. As the GraphQL schema matures, new data types appear.
Make a single call to retrieve (rather than many REST API calls).
Response is structured using the same JSON hierarchy as the call.
Changes can occur with less fuss than REST API.
I couldn’t find a PSGallery module for referencing GitHub’s GraphQL, so I set out to create one when that’s what Karol Kaczmarek suggested I do.
The Functions folder contains Private and Public folders.
More on API Microservices
This is one of a series:
- API Portals
- GraphQL API
- GitHub API
- GitHub GraphQL API
- API Swagger
- API Design Tools
- API Design
- API Programming
- REST API Responses
- API Management Evaluation
- API Management by Microsoft Azure
- PowerShell GitHub API Programming
- PowerShell API Programming
- PowerShell Desired State Configuration
- PowerShell on Mac