-
Notifications
You must be signed in to change notification settings - Fork 1
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
Global search can not get the search result #61
Comments
Hi, @tommychen1228 Could you show logs with response - request. I have checked and I was able to get a result. |
This is the dialogs response, we can see that it contains a message "Asdfasdf", and then we search keyword "Asdf", the request and response is below:
|
@tommychen1228 so it searches for 'exact' match instead of 'contain', right? |
No, no matter whether I use the full text or part of the text to search, no results are returned. Such as: |
@DaveLomber Is the method I used incorrect? |
We prepared a simple script which does the following:
then run it via According to our tests, it successfully returns dialogs if search by Could you please try it at your end and let us know |
@DaveLomber thank you for your reply.As your code, it works well. But I think I found the key point, the dialog created in my app, the type is 3 (1-1 chat), in your code the type is 2. if I change the dialog type to 3 and search, it returned nothing.So, whether the dialog with type 3 does not support search? |
@tommychen1228 thanks for sharing more details For 1-1 chat, we display other user's full_name/login as a chat dialog's name You mean it does not search against other user's full_name/login ? |
@DaveLomber not only the 1-1 chat dialog's name, but also the messages in dialog, can‘t be searched. It seems like 1-1 chat is note supported search. |
I used ConnectyCube.chat.search({search_text:keyword, limit:100}), but no result returned.
We have used 1 to 1 chat, can retrieve the dialogs and chat history.
So, whether if i used in a incorrect way?
The text was updated successfully, but these errors were encountered: