celinanperalta/cs-554-fp

spinder round 2??

we're back with yet another spotify application

1. This app contains a backend server and a frontend nextjs application that both must be installed. Backend Installation:
2. ImageMagick Cli must be installed. This proper version must be version 6 and not 7. -- The legacy website can lead you to the correct version https://legacy.imagemagick.org/script/download.php -- Note that if ImageMagick version 7 is installed in addition to 6, this will not work.
3. Once ImageMagick is installed, the node_modules must be installed for the server. This can be done using "npm install" inside of the top level server folder.
4. Once everything is installed, the server can be started with "npm start"

Frontend Installation:

1. navigate to the src/client directory
2. run "npm install" to install all the needed dependencies.
3. Once everything is installed the client can be started with "npm run dev"
4. navigate to localhost:3000/ and it should redirect you to a login page.

cs-554-fp's Issues

Comment on prompts

Settle on DB design for all tings

Look into ES configuration

• Figure out how to spawn ES instance
• Create single connection to ES in server
• Make a few calls and then write resolvers for GET requests to ES

Spotify search feature

Like submissions

Implement Spotify login

https://jkettmann.com/facebook-login-with-graphql-and-passport

http://www.passportjs.org/packages/passport-spotify/

We can follow the usual Spotify auth flow using graphQL. Outer auth layer is still needed so users not connected to Spotify can poke around the app.

Searching for songs should be available to users not connected to spotify?

Resolver and service for spotify

• Search songs
• Get user playback

Is searching for songs the only endpoint we need?

Pages don't load all the data

in prompts comments/song subs won't load properly idk what to do about this though

Set up server boilerplate

Fix rendering bug for prompts

Update course technologies to Next and GraphQL instead of Redis and Firebase.

Bug(?): After executing login/register mutations, `me` does not return the current user in the context.

After calling ctx.login() in either register or login, ctx.getUser() returns the expected value. Guessing that this doesn't persist in GraphQL sandbox, or something's wrong with how I set up passport.

Add! Linter! Script! Please!

ESLint config file is there, just need to add scripts to package.json and maybe a pre-commit hook in the future (probably not doing that because we will stop caring at some point)

Unhandled exceptions on server side

try catches need to be somewhere not sure tho

Add padding to main layout

Add song submissions to prompts

Clean up imports/require in server files lol

Redis needs to be setup

:|

Check if user is authorized to execute updates on objects (check posted_by id equality)

Set up client boilerplate

Can we use next.js for dis

Set up firebase authentication (no spotify connection)

Do things nicely this time and use `dotenv`

https://menuradewalegama.medium.com/how-to-use-dotenv-with-node-application-b484e3c424ff

For Spotify config, ES things, and everything in between

Move ES functions to `/services` and use `esConnection` in resolvers

Set up Spotify credentials in config

Add auth to queries/mutations using `context.req.session.passport.user` https://jkettmann.com/3-ways-for-authorization-with-graphql-and-apollo