Closed progval closed 9 years ago
Note: I noticed this bug thanks to the integration tests. That's why I did not deploy this update yet
It as a type sentence
, so yes it is a sentence, isn't it?
can we know what is the first release that produced this bug ?
0.4.7
it's not really a bug: before 4.7 there was a error if the first word of the sentence was not a node of the dependency tree (it happens especially for triples, now it's no longer the case (it allows us to support "in wich..." questions for instance).
The only solution we have is to write an algo that determines wether the input is a question or not. Is it really our job (other modules also want to know this)?
Maybe we could play with the accuracy and/or the relevance: if the triple-parser returns something, it must have an higher accuracy/relevance than the thing returned by Grammatical.
So this is not a bug?
I think it is not relevant to our module. This is the same for maths: if you send us maths, we will answer some very weird things.
Since we have never try to detect the type of the input (math, triples, question...), i consider it's not a bug (it was working on your example before because of an assert error that was not designed to detect wether the input is a triple or not)
There is a very tricky bug in the last release.
On the input
{"type": "sentence", "value": "(Douglas Adams, birth date, ?)"}}
, your module returns this object:while it should not return anything (this is not a sentence).