Move schema settings into a new tab

Created on 10 April 2021, over 3 years ago
Updated 31 July 2024, 5 months ago

Altering the "Fields" tab is not so easy, and adding all the required configurations to the "Processor" is complex as well (especially if we want to configure embeddings using Ajax).

The best solution is probably to add a new tab for Schema management and force the user to go to that tab after field configuration. This will give us all the freedom we need.

We must ensure an index without a schema doesn't break the rest of the configuration pages.

Previous summary

The only reasonably quick way I was able to implement the special per-field settings that Typesense requires was to create a processor, and use its access to the index's fields to create a form to provide per-field settings for "facet", and "optional", and to provide a place to set the "default_sorting_field" setting.

It's obvious that it would be better to add these to the main field definition form (an index's "Fields" tab), but I wasn't able to figure out the right way of overriding that fields table's columns.

So the question is: did I miss a good way to alter the table? My experiments with form alter hooks and event subscribers were both unsatisfactory.

📌 Task
Status

Fixed

Version

1.0

Component

User interface

Created by

🇫🇷France bedlam Lyon

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024