Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Soundcloud] Update hardcoded client id #777

Closed

Conversation

XiangRongLin
Copy link
Collaborator

  • I carefully read the contribution guidelines and agree to them.
  • I have tested the API against NewPipe.
  • I agree to create a pull request for NewPipe as soon as possible to make it compatible with the changed API.

In response to: https://github.com/TeamNewPipe/NewPipeExtractor/runs/4766073255?check_suite_focus=true#step:5:304
I personally find the tests bad, because they will regulary break the CI pipeline. But thats my personal opinion

@opusforlife2
Copy link
Collaborator

I personally find the tests bad because they will regulary break the CI pipeline

Is it possible to have a separate test + CI run just for the client ID?

@AudricV
Copy link
Member

AudricV commented Jan 24, 2022

The hardcoded client id has been updated with #768. Closing.

@AudricV AudricV closed this Jan 24, 2022
@AudricV AudricV added the soundcloud service, https://soundcloud.com/ label Jan 24, 2022
@XiangRongLin XiangRongLin deleted the soundcloud_hardcored branch January 24, 2022 18:46
@opusforlife2
Copy link
Collaborator

#777 (comment)

Yes or no? Anyone?

@XiangRongLin
Copy link
Collaborator Author

Is it possible to have a separate test + CI run just for the client ID?

@opusforlife2 Yes, but it requires time to seperate it out properly. If you have the time feel free to do it.

@opusforlife2
Copy link
Collaborator

I have no idea how. xD But now that I know it's possible, we can open an issue for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
soundcloud service, https://soundcloud.com/
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants