keithstric / booleansearchparser Goto Github PK

Tokens which are children (i.e. inside quotes or parens) are not properly identified as children

When initially parsing a search string. The reported rule for a match may be whitespace. However, the token is actually a term and NOT whitespace. This signifies that this part of the search string was actually matched by 2 rules and the rule for a term was the first match, and rule for whitespace was the second match. This signifies that the rule property should be an array.

Add span tags around terms.
Use a non-breaking space for whitespace.
Add div tags to groupings.

For example:

this AND ("other thing" OR that)

Should provide this html:

<span class="term">this</span>&nbsp;<span class="operator">AND</span>&nbsp;
<div class="grouping">
  <span class="paren">(</span>
  <div class="grouping">
    <span class="quote">"</span>
    <span class="term">other thing</span>
    <span class="quote">"</span>
  </div>
  &nbsp;<span class="operator">OR</span>&nbsp;<span class="term">that</span>
  <span class="paren">)</span>
</div>

When a token is an Operator or Possible Operator, it should have the text leading up to the operator. For example:

"this AND that NOT something"

The token for "AND" should have a phrase of "this AND". The token for "NOT" should have a phrase of "that NOT".

Currently, the phrase property of operators is always undefined.

There is currently no way to select the rules or validation rules that will be used for the parsing operation. We should be able to define which rules will be used without having to modify the defined rules.

Not sure this is actually a bug per-se. Maybe "selected rules" is redundant since we always have the default rules to fall back on.