[GH-ISSUE #118] Environmental variables should have the prefix SPOTIFY_ #37

Closed
opened 2026-02-27 20:22:44 +03:00 by kerem · 2 comments
Owner

Originally created by @marioortizmanero on GitHub (Aug 17, 2020).
Original GitHub issue: https://github.com/ramsayleung/rspotify/issues/118

The environmental variable names currently are CLIENT_ID, CLIENT_SECRET and REFRESH_TOKEN. I think it would be a better idea to use these same names with the prefix SPOTIFY_ to avoid name collisions with other programs/libraries that use OAuth2, like SPOTIFY_CLIENT_ID.

By the way, I'll leave for 3-4 days so I won't be able to respond to issues/PRs.

Originally created by @marioortizmanero on GitHub (Aug 17, 2020). Original GitHub issue: https://github.com/ramsayleung/rspotify/issues/118 The environmental variable names currently are `CLIENT_ID`, `CLIENT_SECRET` and `REFRESH_TOKEN`. I think it would be a better idea to use these same names with the prefix `SPOTIFY_` to avoid name collisions with other programs/libraries that use OAuth2, like `SPOTIFY_CLIENT_ID`. By the way, I'll leave for 3-4 days so I won't be able to respond to issues/PRs.
kerem closed this issue 2026-02-27 20:22:44 +03:00
Author
Owner

@ramsayleung commented on GitHub (Aug 18, 2020):

I think it would be a better idea to use these same names with the prefix SPOTIFY_ to avoid name collisions with other programs/libraries that use OAuth2, like SPOTIFY_CLIENT_ID.

I think it will be better to have the prefix RSPOTIFY_ just avoid name collisions with other Spotify libraries.

<!-- gh-comment-id:675200200 --> @ramsayleung commented on GitHub (Aug 18, 2020): > I think it would be a better idea to use these same names with the prefix SPOTIFY_ to avoid name collisions with other programs/libraries that use OAuth2, like SPOTIFY_CLIENT_ID. I think it will be better to have the prefix `RSPOTIFY_` just avoid name collisions with other Spotify libraries.
Author
Owner

@marioortizmanero commented on GitHub (Aug 20, 2020):

That's not a bad idea either. I think collisions with other Spotify libraries aren't that bad because you can share the credentials, but I'd rather keep it trouble-free with RSPOTIFY-

<!-- gh-comment-id:677908847 --> @marioortizmanero commented on GitHub (Aug 20, 2020): That's not a bad idea either. I think collisions with other Spotify libraries aren't that bad because you can share the credentials, but I'd rather keep it trouble-free with RSPOTIFY-
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/rspotify#37
No description provided.