feat: add general purpose search components #2588
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… components and types
…earchSourceResultListEnd
MartinCupela
requested review from
oliverlaz,
myandrienko and
arnautov-anton
|
Size Change: -173 kB (-14.57%) 👏 Total Size: 1.01 MB
ℹ️ View Unchanged
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🎯 Goal
Provide general purpose search components and controller. Allow for absolute search customization.
Depends on
Todo
🛠 Implementation details
Search controller
Coordinates search execution among individual search sources. Allows to combine unknown search sources defined by the integrator. Implements the search state machine.
Base search source
Takes care of common search source task like:
Search source
Class that takes advantage of inheriting from BaseSearchSource. Each search source should defined integrators or the default one is responsible for:
React components
The new components live in
experimental/Searchfolder. This allows for component name duplication compared toChannelSearchcomponents.An important change is the ability to jump from a message search result to that message in the parent channel. Currently the information about the jumped-to-message is stored in the SearchController state, but this should be moved to a future message list controller state.
The searchController instance has been added to the
ChatContext.New component context has been introduced on Chat level to allow consume the context also in the ChannelList. All the newly added components are thus overridable via this context. The new Search component is rendered as opt-in if passed as a prop to
Chatcomponent:Also
ChannelAvatarhas been added to the component context value as a separate key and is prioritized inChannelHeaderandChannelPreview,Out of scope
🎨 UI Changes
VO0L.webm