fix: search with `exact: true`

[vachmara]

🔗 Linked Issue

Closes #866

❓ Type of Change

• [ ] 📖 Documentation (updates to docs or README)
• [x] 🐞 Bug fix (non-breaking change that fixes an issue)
• [x] 👌 Enhancement (improves existing functionality)
• [ ] ✨ New feature (non-breaking change that adds functionality)
• [ ] 🧹 Chore (build process or auxiliary tooling)
• [ ] ⚠️ Breaking change (fix or feature that changes existing behaviour)

📚 Description

With exact: true, the search currently returns documents whose terms partially match the query instead of only those with an exact match.

Why it happens

1. The search code first tokenises the term.
2. For each token, it then checks the radix tree for that same token.

Unfortunetly, neither filters nor facets allow a strict equality between a property value and the full term. Below my proposal.

🛠️ Proposed Solution

1. Keep the current token-level matching.
2. Rename the internal exact flag to something explicit (e.g. exactToken; open to suggestions).
3. Apply the public exact option only when comparing the entire property value to the entire normalised term. (like implemented in this PR)

✅ Status

• [x] Implementation complete
• [x] Tests updated
• [ ] Documentation updated

@algora-pbc /claim #866

[vercel[bot]]

@vachmara is attempting to deploy a commit to the OramaSearch Team on Vercel.

A member of the Team first needs to authorize it.

[padagab12345]

Killyou

[padagab12345]

Chu l

[micheleriva]

chill out or gtfo @padagab12345