ibrahimGit123
commented
1 year ago I was able to solve the issue. The Name Field of the lookup editor (which is what shows the search options) needed to be added with the QuickSearch attribute for it to work properly.
However, I feel this should be default behaviour so that we do not have to remember to add QuickSearch attribute, as it is with regular LookupEditor
volkanceylan
Before submitting the bug report, please read and check the following items
What happened?
When i use ServiceLookupEditor - the search field is not working properly. Note that my code uses Namespaces (not ESM).
In example above, typing 707 does not filter to the proper record. Instead, nothing appears.
What did you expect to happen?
When I start typing, the search result should show the correct options
How to reproduce?
Use a lookup field with ServiceLookupEditor where the options have multiple works
What Serenity Nuget Versions are you seeing the problem on? (separated by comma)
6.48
Relevant log output
No response
Serene template version
No response
Sergen version
No response
Code editor
VS 2022
Operating System
Windows 11
Node.js version
No response
TypeScript version
No response
Database type and version
Azure SQL
On which device do you see the problem?
No response
On which operating system do you see the problem?
No response
On which browsers do you see the problem?
Chrome
On what version of the browsers do you see the problem?
No response
Additional information
No response