Smart Search Comments Block for Solid

Edit REMARKS (the author id, the words, a status and the has list of link, code or image) and PEOPLE. The operators live in OPERATORS, each with a key, the values it takes and an example, so a new operator is one row plus a case in fitsToken.

One regular expression cuts the text into quoted phrases and whitespace-separated words, and each piece is read as an operator, a phrase or a word. A word matches if it appears in the comment, and every chip must match, so adding a chip narrows the results. A chip with a problem is shown with a warning mark and ignored in the search.

The first phrase or word in the query. The component marks one string, so operators are never marked and further words narrow the results without being highlighted. If you need more marks, repeat the highlight for each term in your own code.

The query and the chips live in the page, and the results are filtered from a typed list in memory. To make it real, send the parsed chips (not the raw text) to your search endpoint, and validate operators on the server too: the client check is only help.

The field is named "Search comments", is marked invalid with a described alert when an operator is wrong, and the chips are buttons named "Remove status:flagged". The operator list is a real description list inside a button-controlled section. Each change is read out in the polite status line, and removing a chip returns focus to the field.

The field takes the full width, the chips stay on one line that scrolls sideways so the frame never grows, and each operator row puts its example button beside the name with the explanation under it.