- Issue created by @kingdutch
We have social_search which currently needs to know a lot about the different features that exist in Open Social. For example it has the "group", "content", and "users" search index which require knowledge of how those features work.
This means that if we change things in that feature we also need to update social_search and the order of enabling features also becomes difficult.
The only thing that social_search should do is provide a base configuration for our unified index (
#3348407: Unify search indices into a single index →
) and the view for our "search all" code. As well as any supporting code that might need to be re-used by other features requiring search.
The specific search views for things like content, users, or groups should be moved to the modules that contain those features (like social_node; social_group_flexible_group; or social_user/social_profile respectively). Any changes that need to be made to the index can be housed in those feature modules too using the config_modify module. That way the social_search module can be maintained and enabled without depending on a specific feature.
Active
12.1
Search