Removing Deprecated Methods from Spotify Changes 11/27/24 #1174
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Ok, so after some extra reading they are deprecated for current DEVELOPMENT projects, not published ones, will update to reflect that. |
|
I guess we will keep them until they are no longer listed in the documentation. But it is still necessary to mark them as deprecated. Sounds like the published ones are going to get affected by this eventually as well. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As of November 27th, 2024, Spotify has made changes to their Web API which deprecates several methods:
(Pulled from official updates)
I still need to deprecate some examples as the documentation that references these methods. The affected methods and tests have been resolved as so far.