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
After doing the technical consultation with @sofia-doofinder it has been decided that since at that level the platform has the store_id and it makes sense to have the logic, to know if the search_engine is valid in the update on save, in dooplugins. The plugin is responsible for making a request to the endpoint created by sending the store_id and receive a response if it is valid or not.
If it is valid, it will proceed as usual, if not, the update on save will be marked as deactivated.
The part of doomanager of the wizard of indexes after talking with @IgnacioPursalsZ has been resolved that right now it does not make sense. Since the way it works now the message would be always shown. This is because in the update on save we check the feed_type that is in datasources.options and this at the time of creating a manual index does not exist. The update on save (to maintain compatibility with old clients) if it detects that a datasource.options does not have this value, it interprets it as “product” (this was done for backward compatibility).
This generates the following conflict for the wizard. If we want to make the same detection as in the update on save it will always recognize that it is not suitable (since the manually created ones do not have that field). The case of making that at that point it is not interpreted as product would never show the message but it would give the conflict later.
So it has been reached that at the moment it does not make sense to make any change in the wizard.
Notion: https://witty-pelican-a6c.notion.site/Update-on-save-multi-indice-65e4bd9c37a64231845e2390d27f3ee5?pvs=4
The text was updated successfully, but these errors were encountered: