-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
added open fast trace requirements for backend search #13851
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
added open fast trace requirements for backend search #13851
Conversation
Looks like you forgot to add your changes to the commit (besides the submodules as already mentioned by the bot)? |
Pleaee also include #840 |
@trag-bot didn't find any issues in the code! ✅✨ |
Your pull request needs to link an issue correctly. To ease organizational workflows, please link this pull-request to the issue with syntax as described in https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue:
Examples
|
`req~backend-search.field-search.field-contains~1` | ||
|
||
Fields are searchable for contained words and sequences. Listing entries with the specified field which contains the searched word or sequence. | ||
<!-- Inherent anyfield search is not a requirement, but a neat implementation feature. --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is covered by req~backend-search.field-search.pseudo-fields~1
. Can be linked.
Open Fast Trace style requirements write up for backend search. As part of my bachelor's thesis.
Feedback or additional requirements i missed is appreciated.
Mandatory checks
CHANGELOG.md
in a way that is understandable for the average user (if change is visible to the user)