Keyword Alerts Comments Block for Svelte

Edit AUDIENCES (an id, a label and the channel that person hears it on) and START (each rule has an id, the phrase, the audience and whether it is on). LIMIT is the most rules the demo keeps and SAMPLE is the comment the tester starts with. The channel comes from the audience, so changing a person's channel changes every rule that alerts them.

Each phrase is turned into a regular expression with its special characters escaped, bounded by word edges and matched in any case, so "refund" matches "Refund" and "refunds" does not match "refund". Matches from different rules that overlap are merged into one mark. This is plain pattern matching in the page, not a model; accents, other alphabets and stemming need a better matcher on your server.

Nothing alerts. If its phrase appears in the text, the line under the result names it ("1 rule is off, so “cancel my plan” stays quiet"), so you can see why a comment did not alert. Switching the rule on makes the next keystroke, or the switch itself, mark it and add it to the "Would alert" line.

The rules and the tester. Add rule puts the rule in the list and nothing is saved or sent. To wire it up, save rules from add and flip, run the same matching on the server when a comment is posted (never trust the browser to alert), and deliver the alert on its channel with the comment's link. Keep the tester: it is how people trust a rule before they turn it on.

Every Switch is named for its phrase, the problem for an empty or repeated rule is written under the field and described to it, and a match is marked with a heavy underline and a tint as well as being listed in words. The rules list is a labelled scroll region you can reach with Tab. Each change is read from one polite status line.

The rows stack their chips under the phrase, the Add rule form becomes one column (phrase, who, button) and the tester textarea is full width, with the result block keeping its height so typing never shifts the page.