https://github.com/nickymeuleman/jason-api
Serverless GraphQL API to fetch JaSON(s)
https://github.com/nickymeuleman/jason-api
Last synced: 2 months ago
JSON representation
Serverless GraphQL API to fetch JaSON(s)
- Host: GitHub
- URL: https://github.com/nickymeuleman/jason-api
- Owner: NickyMeuleman
- Created: 2019-08-21T12:37:28.000Z (almost 6 years ago)
- Default Branch: master
- Last Pushed: 2020-03-15T13:41:58.000Z (about 5 years ago)
- Last Synced: 2025-02-27T23:47:27.249Z (3 months ago)
- Language: TypeScript
- Homepage: https://jason-api.netlify.com
- Size: 420 KB
- Stars: 5
- Watchers: 2
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# JaSON API
Too many Jasons?
## Update 9 Match 2020
On I disabled the
serverless functions from running in production.
The site's loading and waving mechanisms have been adjusted to
be **visually identical** to when the serverless functions
were online. As a result, waves are no longer sent to the database and
will not be counted.
To view the code of this site when serverless functions were enabled,
check out [the repository at the last state with serverless functions enabled](https://github.com/NickyMeuleman/jason-api/tree/dfb0a7f2469fef55aa4f616b9e181d09bf40007b)
Only a few lines of code are different. The different lines were
commented out and replaced immediately below.
To view the code that moved away from serverless functions, check
out [the pull request that removes serverless functions](https://github.com/NickyMeuleman/jason-api/pull/6)
## Pre 9 March
### Is the `firstName` field just a hardcoded `"Jason"` string?
Yes, yes it is.
### Notes
Some mutation are commented out in the schema (as are their respective resolvers).
They are fully functional, but disabled because the GraphQL playground is open and I don't want the internet to have free reign over the database 🤷♂