Skip to content
This repository has been archived by the owner on Dec 21, 2023. It is now read-only.

Passing invalid configurations (last.fm and Twitter, consumer and app). #7

Open
4 of 6 tasks
Tracked by #6
soup-bowl opened this issue Dec 24, 2021 · 0 comments
Open
4 of 6 tasks
Tracked by #6

Passing invalid configurations (last.fm and Twitter, consumer and app). #7

soup-bowl opened this issue Dec 24, 2021 · 0 comments
Assignees
@soup-bowl
Labels
bug Something isn't working

Comments

@soup-bowl
Copy link
Owner

soup-bowl commented Dec 24, 2021 •
edited
Loading

As of writing this ticket, unknown to author what transpires when missing or incorrect information is fed to last.fm/Twitter API. Assuming an uncaught exception.

  • last.fm - no key.
  • last.fm - Invalid key.
  • last.fm - User specified incorrect Lfm name.
  • Twitter - no application identity.
  • Twitter - Invalid app ID.
  • Twitter - Client auth keys are incorrect.
@soup-bowl soup-bowl mentioned this issue Dec 24, 2021
Open
3 tasks
@soup-bowl soup-bowl self-assigned this Dec 24, 2021
@soup-bowl soup-bowl added the bug Something isn't working label Dec 24, 2021
soup-bowl added a commit that referenced this issue Jan 11, 2022
@soup-bowl
Handle incorrect Twitter API creds (#7).
5933e57
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@soup-bowl soup-bowl

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@soup-bowl