[LUCENE-8001] UnescapedCharSequence Bugs

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 7.1
• Component/s: core/queryparser
• Lucene Fields: New
• Assignee: Unassigned
• Reporter: Shad Storhaug
• Created: 20/Oct/17 11:38
• Updated: 28/Aug/22 15:20

Description

There are a couple of issues with UnescapedCharSequence:

1. The private constructor is not used anywhere (and if it were, it would throw exceptions)
2. The ToEscapedString() overload has an invalid condition that will only evaluate to true if the string has a length of 0.

There are no tests for UnescapedCharSequence so these issues have gone unnoticed for quite some time.

Issue Links

• is related to: LUCENENET-592 Lucene.Net.QueryParsers.Flexible.Core.Util.UnescapedCharSequence