Fix exact match profanity
Bug: 8661070 Change-Id: I421bed14cc71af7715101423652d706e33958445main
parent
7b2114a428
commit
df2eae6e69
|
@ -164,8 +164,8 @@ int Suggest::outputSuggestions(DicTraverseSession *traverseSession, int *frequen
|
|||
const bool isPossiblyOffensiveWord = terminalDicNode->getProbability() <= 0;
|
||||
const bool isExactMatch = terminalDicNode->isExactMatch();
|
||||
const int outputTypeFlags =
|
||||
isPossiblyOffensiveWord ? Dictionary::KIND_FLAG_POSSIBLY_OFFENSIVE : 0
|
||||
| isExactMatch ? Dictionary::KIND_FLAG_EXACT_MATCH : 0;
|
||||
(isPossiblyOffensiveWord ? Dictionary::KIND_FLAG_POSSIBLY_OFFENSIVE : 0)
|
||||
| (isExactMatch ? Dictionary::KIND_FLAG_EXACT_MATCH : 0);
|
||||
|
||||
// Entries that are blacklisted or do not represent a word should not be output.
|
||||
const bool isValidWord = !terminalAttributes.isBlacklistedOrNotAWord();
|
||||
|
|
Loading…
Reference in New Issue