BUG: crossref keyword ignored in search
The results with or without the crossref keyword are identical. They shouldn't be.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
Comments
-
I don't think your second query expresses the problem as it should show just the second term.
Dave
===Windows 11 & Android 13
0 -
The cross-reference field is incompatible with the milestone keyword, so it just gets ignored. Do you think it would be better to show an error?
0 -
Do you think it would be better to show an error?
Definitely. Any time the machine thinks it should execute something other than what was asked for, it should generate an error. The alternative of simply ignoring what it doesn't like appears to the user as inconsistent, flakey behavior.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
Do you think it would be better to show an error?
+1 [Y] for showing an error: would rather see red box error than something silently ignored
Keep Smiling [:)]
0 -
The cross-reference field is incompatible with the milestone keyword, so it just gets ignored. Do you think it would be better to show an error?
Yes. As they are incompatible, the parser should indicate that the second keyword is "unexpected" (currently it prefers milestone).
Dave
===Windows 11 & Android 13
0
