-
Notifications
You must be signed in to change notification settings - Fork 32
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
Add possibility to search for all app users in mentions #144
Comments
szuperaz
changed the title
Add possibility to search for all app users for mentions
Add possibility to search for all app users in mentions
Nov 24, 2021
szuperaz
added a commit
that referenced
this issue
Nov 29, 2021
BREAKING CHANGE: You need to call `forRoot` when importing the `StreamChatModule`
szuperaz
added a commit
that referenced
this issue
Nov 29, 2021
BREAKING CHANGE: You need to call `forRoot` when importing the `StreamChatModule`
szuperaz
added a commit
that referenced
this issue
Dec 1, 2021
BREAKING CHANGE: You need to call `forRoot` when importing the `StreamChatModule`
szuperaz
added a commit
that referenced
this issue
Dec 1, 2021
BREAKING CHANGE: Besides `StreamChatModule` you also need to import `StreamAutocompleteTextareaModule` or `StreamTextareaModule`
github-actions bot
pushed a commit
that referenced
this issue
Dec 1, 2021
# [2.0.0](v1.4.2...v2.0.0) (2021-12-01) ### Features * Implement user mentions [#143](#143) [#144](#144) ([2354393](2354393)) ### Performance Improvements * Remove unnecessary message-input components ([14e5177](14e5177)) ### BREAKING CHANGES * Besides `StreamChatModule` you also need to import `StreamAutocompleteTextareaModule` or `StreamTextareaModule`
🎉 This issue has been resolved in version 2.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add parameter that decides if we should do a local search (channel members) or backend search with all app users included for mentions
The text was updated successfully, but these errors were encountered: