# LibTmux.Query.QueryEdgeParser

- **Module:** LibTmux.Query
- **Package:** LibTmux
- **Language:** .NET
- **Kind:** class
- **Source:** https://github.com/libtmux/libtmux-dotnet/blob/320dc64f4b8b7815842471327a5e6b84a1499bf8/src/LibTmux/Query/NameContainsLookupParser.cs#L18
- **Page:** https://libtmux.org/en/dotnet/latest/reference/libtmux-query-queryedgeparser/

Parses the one legacy lookup spelling this port still carries.

Python accepts a whole family of <c>field__operator</c> lookups. Only
<c>name__contains</c> survives here, as a migration aid for callers porting
keyword-argument filters. New code writes an expression and lets translation
build the document.

This deliberately diverges from Python: there, an unrecognised
operator falls back silently to an exact match. Answering a
different question than the one asked is the failure this port
refuses.

## Members

- `ParseNameContains` (method): Parses a <c>name__contains</c> lookup into a query document.
