This application uses Google Books API to search for books and enables users to save the results under their own accounts.
- Description
- Table of Contents
- Technologies
- Tasks List
- Screenshots
- Available Scripts
- Learn More
- Deployed Application
- Questions
- React
- GraphQL
- JSON Web Token (JWT)
- Apollo Server and Provider
- Google Books API
- Node
- Express
In this project I have done the following changes in the existing code of book-search application:
-
Setting up an Apollo Server to use GraphQL queries and mutations to fetch and modify data, replacing the existing RESTful API.
-
Modifying the existing authentication middleware so that it works in the context of a GraphQL API.
-
Creating an Apollo Provider so that requests can communicate with an Apollo Server.
-
Deploying the application to Heroku.
Please see below animations for different sections of this application:
- As you can see in the following animation, a user can type a search term (in this case, "star wars") in a search box and the results appear:
- The user can save books by clicking "Save This Book!" under each search result, as shown in the following animation:
- A user can view their saved books on a separate page, as shown in the following animation:
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.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
Please use the following link to view the deployed application on Heroku: Deployed App
If you have any questions please use the following two links to contact me: