This seems to be broken
guibor opened this issue · comments
Presumably a change in how powerthesaurus.org returns results
It would appear that powerthesaurus changed both where it keeps the json store (that this package uses to extract suggestions) and its structure. I tried to make sense out of it but it seemed unnecessarily complex, so I modified the package to extract synonyms from the html body instead.
If @SavchenkoValeriy is ok with it, I can open a pull request.
@maxchaos
it seems @SavchenkoValeriy temporarily has no time to handle this. So you can first commit it to your fork that we can use it :)
I've already done so in a different branch, namely pt-api-change. I believe I should wait for @SavchenkoValeriy's response a bit longer before I merge it into master (unless this is inconvenient to you), since he may be able to fix this without dropping json store support.
It's ok. I am using your pt-api-change branch now, thanks!
^ up
@maxchaos Been a while, maybe time to merge?
@dleslie I guess so.
Now, How to sove this issue to make this package work?
I've used your fix for a while, @maxchaos, thanks for making it public! I noticed yesterday that it stopped working for me though. I'm just wondering whether it's still working for you and if not, whether you have any thoughts on how to fix it?
@marlinstrub Indeed, trying to fetch a page from powerthesaurus falls through with status code 403 (forbidden). It would appear that powerthesaurus is dropping http requests without certain header arguments (the reason why eludes me). Also, there was a change in the response format. I just pushed a fix on my fork's master branch that should work around both of these issues. Let me know if it works for you.
@maxchaos Works like a charm, thanks a lot!
Great. For the record, these past few fixes have been merged into the master branch of the original repo so there is no need to pull from my fork. As such, I'll be closing this issue.
Even better, thanks!