Skip to content

Help: how a wildcard stops before later elements (engine 4.2.27) - #239

Merged
ddehilster merged 1 commit into
VisualText:mainfrom
ddehilster:docs/smart-wildcard-427
Oct 14, 2026
Merged

ddehilster merged 1 commit into
VisualText:mainfrom
ddehilster:docs/smart-wildcard-427

Conversation

@ddehilster

Copy link
Copy Markdown
Member

Documents VisualText/nlp-engine#783 (#427) on the _xWILD page.

The new text covers three points:

  • An unrestricted wildcard stops at the first node the elements after it can match, and matching never backs up.
  • From 4.2.27, when an optional element follows the wildcard, a later element (up to the next required one) also stops it, and the optional element is then absent.
  • On a tie at the same node, the optional element is used.

I ran the example on the page through the 4.2.27 build: on "the big bears met three bears" the rule matches "the big bears", as the page says. On 4.2.18 the same rule doesn't match at all, which is what the "before" sentence describes.

Merge after nlp-engine#783.

🤖 Generated with Claude Code

… 4.2.27, #427)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ddehilster
ddehilster merged commit 485e720 into VisualText:main Oct 14, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant