Removed refresh token route and accepting access tokens through headers and added @apollo/client #36
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes accordingly to folder structure:
Server
Earlier Flow
Flow Now
pglibrary version, now the server can perfectly connect with the ```postgres`` database.refresh_tokenroute fromindex.tsfile, as passing access tokens through headers is way more efficient and optimized than explicitly requesting them through a route.isAuth.tsmiddleware to handleaccess_tokenas well asrefresh_token. If theaccess_tokenis expired, newaccess_tokenis generated and sent through the request's headers.userIdaspayload, entireuserdetails are passed.Web
@apollo/clientpackage and removed unused packages.access_tokenwith the headers with every graphql request and receiving them with the response headers.