Skip to content

Conversation

germanosin
Copy link
Member

  • Breaking change? (if so, please describe the impact and migration path for existing application instances)

What changes did you make? (Give an overview)

Is there anything you'd like reviewers to focus on?

How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

  • No need to
  • Manually (please, describe, if necessary)
  • Unit checks
  • Integration checks
  • Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
  • My changes generate no new warnings (e.g. Sonar is happy)
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged

Check out Contributing and Code of Conduct

A picture of a cute animal (not mandatory but encouraged)

@germanosin germanosin requested review from a team as code owners October 2, 2025 10:47
@kapybro kapybro bot added status/triage Issues pending maintainers triage status/triage/completed Automatic triage completed and removed status/triage Issues pending maintainers triage labels Oct 2, 2025
@germanosin germanosin linked an issue Oct 2, 2025 that may be closed by this pull request
2 tasks
@germanosin germanosin added this to the 1.4 milestone Oct 2, 2025
@Haarolean Haarolean added the hacktoberfest-accepted PRs accepted towards hacktoberfest goal and will be counted as approved label Oct 5, 2025
@germanosin germanosin merged commit 5ba27d9 into main Oct 8, 2025
14 of 15 checks passed
@germanosin germanosin deleted the issues/1333-optional-fts branch October 8, 2025 07:58
@github-project-automation github-project-automation bot moved this from Todo to Done in Release 1.4 Oct 8, 2025
@Haarolean Haarolean added type/enhancement En enhancement/improvement to an already existing feature scope/backend Related to backend changes area/messages labels Oct 8, 2025
@Haarolean Haarolean changed the title Issues/1333 optional fts BE: Implement per request FTS control Oct 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

hacktoberfest-accepted PRs accepted towards hacktoberfest goal and will be counted as approved scope/backend Related to backend changes status/triage/completed Automatic triage completed type/enhancement En enhancement/improvement to an already existing feature

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Support per-request control for enabling/disabling FTS

2 participants