The simplest example connecting to a GraphQL API. Uses the generic javascript Apollo client, that works with plain javascript or with any framework.
Base UI repository - https://github.com/RafaelFS/graphql-example-layout
Repository with the UI used in the example, without any integrations - a clean slate
REST API Example - https://github.com/RafaelFS/graphql-example-initial-rest-version
Repository with the example connecting to the REST API version. Intended to use as a comparison with the GraphQL examples.
GraphQL Client Example - https://github.com/RafaelFS/graphql-example-with-client
The simplest example connecting to a GraphQL API. Uses the generic javascript Apollo client, that works with plain javascript or with any framework.
GraphQL React Example - TBA - Example connecting to a GraphQL API. Uses the React specific components to do so.
GraphQL Typescript Example - TBA - Build upon the last examples by adding Typescript and using the automatic code generation.
This project was bootstrapped with Create React App.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.