-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Update howlongtobeat extension #17079
base: main
Are you sure you want to change the base?
Conversation
- Title case and publish command in package.json - Fix error: Hash not found by changing search endpoint from api/s/ to api/ouch/ - Initial commit
Thank you for your first contribution! 🎉 🔔 @Cronos87 @whitespacecode @ridemountainpig you might want to have a look. You can use this guide to learn how to check out the Pull Request locally in order to test it. Due to our current reduced availability, the initial review may take up to 10-15 business days |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me too. Many thanks for the fix 🙏🏻
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Request a new review when you are ready. Feel free to contact me here or at Slack if you have any questions.
Change the title back to HowLongToBeat
Co-authored-by: Per Nielsen Tikær <[email protected]>
Description
Recently I downloaded this extension and noticed that the search didn't work at all, I was always getting 'Could not perform search Error: Hash not found'. I went to howlongtobeat.com and tried searching for a game and checking where the request goes to. It was api/ouch/, so i forked the extension, changed the endpoints used in the code, and this seems to have fixed the issue!
Screencast
Checklist
npm run build
and tested this distribution build in Raycastassets
folder are used by the extension itselfREADME
are placed outside of themetadata
folder