[v2] SenseIds are not appearing in Sentences
Categories
- 269 All Categories
- 4 LexiStats Corner
- 12 Review my code
- 6 Tutorials and presentations
- 89 Frequently asked questions
- 5 How to get useful technical help
- 2 Member guidelines
- 12 Suggest an improvement
- 54 Report a bug
- 7 Ask the Community: Other
- 51 Ask the Community: Technical and operational questions
- 53 General
[v2] SenseIds are not appearing in Sentences
shahood
Member ✭✭
in Report a bug
Hi @AmosDuveen
I've noticed that 'senseId' field is totally missing in the sentences retrieved via Sentences endpoint.
As an example, please check 'flush', 'native', 'absolute' but this issue is with every word I've checked so far.
Looking forward to a quick fix!
Thanks
Comments
Hi @AmosDuveen @Simone
Hopefully u guys have checked out this and other V2 related issues...
Hi @shahood,
Thanks for feeding back all of these issues, I have passed them onto our developers to investigate.
Hi @AmosDuveen
Should we expect a fix any time soon?
Hi @AmosDuveen
I'm eagerly waiting for a response. A complete feature in my app is going wasted due to this issue. Can u please follow it up with the Dev team more closely?
Thanks!
Hi guys,
Its been almost two months since I reported this issue. The last comment said that it has been forwarded to the dev team to investigate but the results of investigation have not been posted here.
Would really appreciate if u could at least declare it as a bug and say that someone is going to fix it OR if it ain't a bug, pl let us know how.
Looking forward to a prompt response!
Best regards
Hello @shahood
Thank you very much for your comment, and for flagging this up to us.
I was informed that this issue will be fixed and should be included in the next release.
Hi @TaisFukushima
Thanks for the reply.
Can u pl let me know when I should be expecting the next release? A tentative date will suffice.
Thanks
Hello,
It has been a month a half since the last post on this issue and the sentences endpoint is still not returning senseids. Could someone shed some light on what is going on please? This was working just fine with V1 of the API.
This endpoint is only open for paid plans so at least some customer support should be offered.
Thanks!
Hello @shahood @knikolov356
I was informed that this issue will be fixed and should be included in the next release.
We are aiming to release the next update v2.1 late July.
Thanks again for flagging this up to us!
@TaisFukushima @knikolov356
This issue is fixed now.