-
Notifications
You must be signed in to change notification settings - Fork 15
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
Fix for newly broken #16
Comments
Hey @felixhirschfeld Thanks for this code! I've tested it on my Deck and it looks to work and I've made a PR for the changes (#17) |
@subnebula cool. Glad it still works I thought they changed it again. |
Potentially, I did have to modify the request body as well to get the queries working. I will test over the next couple of days and see if the API calls still work, maybe they have something else that changes daily as well |
How does one use this code? Is it just via konsole on linux? Is it more complicated? Please provide the steps for a newbie! |
@danigarvire not that simple I'm afraid. Decky plugins require a bit of experience working with node. If you don't already know how to develop and build a node app it is likely a bit too complicated and not something I can provide steps for. You'd be best to wait until the fix is merged in and then you can install it from the decky store as usual. |
@subnebula hi, can you build it for us? and pack it to zip? so we can install it from decky manually? |
@subnebula Oh! After googling for a little while i understand that it might be a bit too hard for someone inexperienced. Hopefully the newly broken HLTB can be fixed! Please update us and let us know if we can help in any way! |
Hello, |
@subnebula I manually edited /home/deck/homebrew/plugins/hltb-for-deck/dist/index.js to incorporate your changes, and it worked for a few days. But it seems to be broken again. |
Yep, looks like they have changed the api again, the requests now go to /find instead of /search, and there might be a bunch of other changes as well. In my brief testing just now I've not been able to make a successful api call to the new endpoint. Looks like we're out of luck with this fix |
I opened new PR #18 for syncing up with the latest HLTB API changes. I had to peek on ScrappyCocco/HowLongToBeat-PythonAPI#35 PR to find new changes they added to API. |
Can confirm that PR 18 works after editing the existing json to match the changes |
Hello Thank you |
I added ZIP and TAR archives to the MR. You can try installing them via Developer Mode of Decky (Decky Settings -> General -> Enable Developer Mode. Then in Settings go to Developer -> Install Plugin from ZIP File and select the ZIP archive. After installing go to Plugins in Settings, select HLTB for Desk settings and then Reload). |
I do not mind taking responsibility for this plugin, since I like it and use it a lot on Steam Deck. @safijari, your opinion is greatly appreciated regarding the matter. |
It worked !! |
Does this mean we can update the plug in now and it will work? |
You should just fork and republish, this fork seems dead |
The API has changed again and PR #18 stopped working while still being not merged. I will publish future fixes under my fork: https://github.com/morwy/hltb-for-deck/releases. |
@morwy Thanks for the fix, it works well (for now...) If the API keeps changing this often, changing the name manually everytime is not very efficient. Using "//api/[a-zA-Z]*" or something similar might be more robust when checking for the pattern in the initial script. It will not cover possible changes they might make on the concatenation part that contains the key, but it'll at least help for future url name changes. The actual API name could be retrieved using the aforementioned pattern in the initial script and re-used dynamically when needed to get game data instead of copying manually the api name everywhere. |
Hey everyone. Unfortunately I don't have a development environment for Decky plugins so I'll just paste some code here.
This should fix the plugin theoritically:
The text was updated successfully, but these errors were encountered: