Yes, that's the one, @Sfaci ! I've updated the description to reflect the correct original start date.

If there is at least one suggestion in the current section, and the user acts on all of them, should the 'View suggestions' button appear (assuming there are suggestions outside the section)?

In T407664#11905384, @Wellverywell wrote:

@medelius I tested RegExps for a bit. They are amazing! But I still found a few bugs, not sure whether in my edit checks or in the code.

1. \w doesn't capture Cyrillic letters. I think this is a JavaScript limitation, but still -- what should we do for this? Would \p{Script=Cyrillic} work (I don't know if EditCheck's RegExps use u flag) or should we use [а-яё] as right now? Both are significantly more verbose than just \w.

In T407664#11910430, @Wellverywell wrote:

My first feedback is that, I think, preserveCase should be true by default for replace rules.

@medelius Right now I also thought that it should be false for case-sensitive rules -- not sure if anything could break if not, but I think there are almost no cases where PC could be useful for case-sensitive patterns.

I've updated those examples. Thanks for pointing this out!

Sure thing! It's been added.

We've implemented regex support! I've updated the TextMatch documentation, but below is the most relevant information you'd need to start using the regex configs. Any feedback on this is appreciated.

Mikhail did a code review pass, so I think we could say that?

In T422931#11867284, @bmartinezcalvo wrote:

I've reviewed the implemented survey and these are some design details to fix:

1. Title text should use the heading style (18px size)
2. Use @background-color-base in the bottom sheet
3. The X button is not well aligned on top with the bottom sheet's title
4. Bottom sheet's paddings (right, left, top, bottom) should be 16px (now it's 12px)
5. The "Submit feedback" button is not visible

Implementation	Design (expected behavior)

Peter, it looks like it didn't ride the train last Monday. Not sure if there's a reason I'm missing there? There was no train last week, so you wouldn't see it on enwiki until Thursday, if that's where you're trying.

Sorry Peter, that still had dummy data on it. We're getting the data we expect now (2), and the graphs are updated and filters are at the top (1).

I've gotten context from David L and will begin working on this!

We discussed this in our planning meeting. @Sdkb brought up a good point that once we publicize TextMatch more, we may (hopefully!) start seeing many changes, which could make alerts overwhelming or unhelpful. What if rather than a "notification" approach, we implement a page similar to Special:EditChecks where we can see how different wikis have configured TextMatch? This could be a more helpful approach long-term and would still provide the awareness we want, so long as we check it.

Documenting the metrics we've decided on:

• time to generate actions, sync and async, on a per-check level; computed each time the checks are run and tracked for a randomly selected 1% of sessions
• an aggregate of typing lags (avg, p50, p95, max) for each session

Ok, I've filed T423021 for TextMatch and T423022 for RequiredTemplateParams.

Ok, I did some digging. Here's a summary of my observations so far. I'll continue to dig today/tomorrow.

Peter, I was with you at first, but @DLynch gave me some helpful context: