allow multiple indexers for one collection#1
Open
T-Mike wants to merge 1 commit into
Open
Conversation
This file contains hidden or 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
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.
Hi,
Just added meilisearch to a new directus project and your work saved me a lot of time!
Because the project I work on is multilingual, I needed to be able to make an index per collection per language.
i.e : collection1_en, collection1_fr, collection2_en, collection2_fr etc...
The most logical way I could think of was change the config file structure by replacing
collectionskey forindexes.Let's take an example:
There are two indexes, designer_en and designer_fr and they are completely separated. Meaning you can do whatever you want with each one.
The code provided works, I did not see any bug related to it but it is not battle tested.
Hope this helps!