helper script
#!/usr/bin/env bash
# Transfers a file from local to remote
PATH_TO_FILE=$1
IP=$2
USERNAME=$3
{ | |
"$help": "https://aka.ms/terminal-documentation", | |
"$schema": "https://aka.ms/terminal-profiles-schema", | |
"actions": | |
[ | |
{ | |
"command": "paste", | |
"keys": "ctrl+v" | |
}, | |
{ |
VITE_apiKey=zahtddfrsfSyCHJYZaDa9s47oP4L7Cc
VITE_authDomain=firebaseapp.firebaseapp.com
VITE_databaseURL=https://firebaseapp.firebaseio.com
VITE_projectId=firebaseapp
VITE_storageBucket=firebaseapp.appspot.com
VITE_messagingSenderId=200000020053535353535353535353
VITE_appId=1:50000000080792:web:6676767676d766d7676sw6
After working with the github rest api and experiencing some of it's limitations it's time to pick things up a bit and dive into their Graphql api
as Usual first things first we set up a tesing enviroment and github provides their own explorer which will setup the authentication headers for you under the hood , but if you prefer to use another gql explorer , just set it up like below Replace ghp_LBgN6pCeWsHcxeoJpR4ZTwUj with your personal access token
I have another article i made about react-query tips an tricks which might help explain that part . becau
was working on a react vite app and had to port it over to Next Js the ported next js app and i very quickly discovered that localStorage worked a little differently n Nextjs and i need it because that's where i was saving my personal access token and theme preferences which lead me down a rabbit hole which resulted in the following custom hook for that