Thanks to visit codestin.com
Credit goes to github.com

Skip to content

feat: extract BuildFuzzinessQueryClauses as public API#266

Merged
silenceqi merged 4 commits intomainfrom
fuzziness_query
Jan 16, 2026
Merged

feat: extract BuildFuzzinessQueryClauses as public API#266
silenceqi merged 4 commits intomainfrom
fuzziness_query

Conversation

@SteveLauC
Copy link
Member

@SteveLauC SteveLauC commented Jan 16, 2026

  • Extract the fuzziness query construction logic from buildFuzzinessQuery() into a reusable public function. This allows clients to build custom hybrid or semantic searches while reusing the framework's fuzziness query logic.

  • Refactor buildFuzzinessQuery() to use BuildFuzzinessQueryClauses()

  • Add SetFuzzinessBuilt() setter to allow clients to skip built-in fuzziness query construction when handling it themselves

Standards checklist

  • The PR title is descriptive
  • The commit messages are semantic
  • Necessary tests are added
  • Updated the release notes
  • Necessary documents have been added if this is a new feature
  • Performance tests checked, no obvious performance degradation

SteveLauC and others added 4 commits January 16, 2026 11:33
* Extract the fuzziness query construction logic from buildFuzzinessQuery()
  into a reusable public function. This allows clients to build custom
  hybrid or semantic searches while reusing the framework's fuzziness
  query logic.

* Refactor buildFuzzinessQuery() to use BuildFuzzinessQueryClauses()

* Add SetFuzzinessBuilt() setter to allow clients to skip built-in
  fuzziness query construction when handling it themselves

Co-Authored-By: Claude <[email protected]>
@SteveLauC SteveLauC marked this pull request as ready for review January 16, 2026 04:01
@silenceqi silenceqi merged commit 9e9931d into main Jan 16, 2026
4 checks passed
@silenceqi silenceqi deleted the fuzziness_query branch January 16, 2026 07:56
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.

3 participants