search

kennethngyen / cse110-triton-music

0 stars 0 forks source link

Implemented spotify webapi for search page functionality #53

Closed JZ0ro closed 1 day ago

JZ0ro commented 5 days ago

Would replacing the client ID and client secret in the .env with MY client ID and secret be sufficient to solve the issue of MY client ID and secret being visible?

Basically, would it be ok if I just replaced the already existing client id and secret with my client id and secret to solve the issue of my client id/secret being present

k3liang commented 5 days ago

my client id and secret in the .env file should be good. Just remove anything like from the actual source code and then get my client id and secret with process.env.CLIENT_ID and process.env.CLIENT_SECRET also remove the axios dependency because I don't think you are using it either.

k3liang commented 5 days ago

additionally, you can look at my code, and you'll see that I have an easy way of calling the spotify endpoints, so you don't have to repeat code like for getting the albums: just await fetch(/userinfo?url=[Spotify API endpoint url])

JZ0ro commented 5 days ago

so update,

when I use your client id and secret, I get this following error: image

But this error disappears when I use my client id and secret. As a work around I was thinking of creating a separate client id variable and client secret var in the .env file and calling it from my file that uses the search engine. Any thoughts on this approach?

Also just throwing out ideas as to why this happens, as I have no idea why it happens, maybe it occurs because your client id and secret is not tied to a premium account?

k3liang commented 5 days ago

can u please commit and push the buggy code? As well as tell me how to reproduce the bug.