You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe this module should behave no differently than how the other backend plugins behave.
The addIndex() method was previously commented out and disabled. When creating a new index, a new collection should be made in Typesense as well.
The previous reason seemed to involve the lack of an initial field with default sort field, which Typesense requires on creating a new collection. We can simply add 'id' or 'uuid' as the first field and the sort field so the process of creating and managing an index in Search API is a bit more streamlined. All entities have a ID/UUID.
Later, we can prevent 'removal' of fields if they are set as the default sort and get it locked and try to keep the fields UI congruent to what Typesense expects at a minimum.
If the index has no fields, add a default one. It would be critical to also add one to the index in Drupal so its 'mapped' in the UI. This is not similar to how other backends work, but its what Typesense requires so that should not be a problem necessarily.
The text was updated successfully, but these errors were encountered:
I believe this module should behave no differently than how the other backend plugins behave.
The addIndex() method was previously commented out and disabled. When creating a new index, a new collection should be made in Typesense as well.
The previous reason seemed to involve the lack of an initial field with default sort field, which Typesense requires on creating a new collection. We can simply add 'id' or 'uuid' as the first field and the sort field so the process of creating and managing an index in Search API is a bit more streamlined. All entities have a ID/UUID.
Later, we can prevent 'removal' of fields if they are set as the default sort and get it locked and try to keep the fields UI congruent to what Typesense expects at a minimum.
It currently looks something like this:
If the index has no fields, add a default one. It would be critical to also add one to the index in Drupal so its 'mapped' in the UI. This is not similar to how other backends work, but its what Typesense requires so that should not be a problem necessarily.
The text was updated successfully, but these errors were encountered: