Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Follow-up to #6666: Query parser: a one-item quoted list loses its literal status

Closed
#6,752 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

A pull request for this has already been merged.

  • #6666 by @rbuergi — merged

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
search

Research direction

Start in the query parser's namespace alternation branch, which only accepts multi-value lists, and the reserved-qualifier pass that rewrites * to Like. Reproduce with namespace:("x*") and -namespace:("x*") in a failing test before changing anything. Done means the quoted one-item list stays literal in both positive and negated forms, either by keeping per-value quotation metadata or by treating a one-value In/NotIn as literal membership. Pick one approach and confirm the existing parser tests still pass.

Written by the indexing model from the issue text.

Description

bug feature:unanchored-queries sev:M

Follow-up to #6666 (review findings deferred from that pull request; Refs #6666).

  • namespace:("x*") yields In with Literal = false; the namespace alternation branch takes only multi-value lists, so the reserved-qualifier pass sees * and rewrites it to Like, and -namespace:("x*") becomes a positive Like. Preserve per-value quotation metadata, or treat a one-value In/NotIn as literal membership.

These are automated-review findings, assessed from the diff and not reproduced; each needs a failing test before its fix. Deferred from the PR because CI is saturated and none of them is a security hole, data loss or a broken build/test.

Dominant language
C#
Stars
12
Forks
5
Avg merge
5h 34m
Merged PRs (30d)
960

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Systemorph/MeshWeaver

All issues in Systemorph/MeshWeaver

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.