Regex Lab
Regex Word Boundary Guide
Use word boundaries for tokens, IDs and search terms without surprising Unicode or punctuation behavior. This page is written as a practical engineering reference: it starts with evidence, keeps risky assumptions visible and links the next useful Formalint checks.
Use it when a ticket, incident or pull request needs a repeatable explanation rather than a quick guess. Keep secrets, customer data and production tokens out of browser tools and shared notes.
When this page is useful
- You need a small, shareable diagnostic sequence.
- You want to compare shell output, payload shape or parser behavior before changing code.
- You are preparing notes for another developer, DBA or support engineer.
Practical workflow
| Step | What to verify |
|---|---|
| Scope the pattern | Decide whether the expression validates a whole value or extracts a fragment from a larger text. |
| Test real edges | Use empty values, copied text, long strings and invalid samples before trusting one green match. |
| Keep policy separate | Let regex check text shape; keep account rules, permissions and deliverability in application logic. |
Command or pattern to start with
\buser\bReview checklist
- Confirm the environment where the symptom happens.
- Use a redacted sample that is still realistic enough to reproduce the behavior.
- Keep request headers, payloads, logs and timestamps together.
- Change one variable at a time so the result stays explainable.
- Link the final note to a related Formalint reference for the next person.
Common mistake
The common trap is treating one matching example as proof that the expression is safe for every user input.
Formalint is strongest when it becomes part of the incident rhythm: reduce the sample, format the evidence, verify the assumption and only then change the system.
Related Formalint references
Continue with Regex Tester, Regex Examples, Complete Regex Guide.
Frequently asked questions
Can I paste production data into this workflow?
No. Use redacted or synthetic examples. The workflow is about evidence order, not copying sensitive systems into a browser.
Is this a replacement for logs and tests?
No. Treat it as a field guide that helps you decide which logs, tests and commands matter first.