@lotics/cli 0.156.4 → 0.156.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/docs/knowledge_docs.md +4 -1
- package/package.json +1 -1
package/docs/knowledge_docs.md
CHANGED
|
@@ -98,7 +98,10 @@ knowing. As an expression, `C/O (Form E)` searches for `C/O Form E` — not in t
|
|
|
98
98
|
returns a confident zero; `[CŨ]` becomes a one-character class and matches every `C` in the
|
|
99
99
|
corpus. Both look like ordinary answers. A literal search has no such failure: the worst case
|
|
100
100
|
is an expression sent without the flag, which finds nothing and says so, naming the search that
|
|
101
|
-
ran and what to pass instead.
|
|
101
|
+
ran and what to pass instead. That last part is **measured, not guessed** — an empty result tells
|
|
102
|
+
you whether reading the pattern as an expression would have matched, so an alternation sent without
|
|
103
|
+
the flag (`phrase A|phrase B`) comes back naming `regex: true` rather than advising you to shorten a
|
|
104
|
+
pattern that was never too broad.
|
|
102
105
|
|
|
103
106
|
### Matching options
|
|
104
107
|
|