work in progress, add search keyword update action

[sebbulon]

WIP, added search keyword action

[hajoeichler]

👍

[sebbulon]

@PhilippSpo happy for me to merge this? Tests go green :)

[emmenko]

@sebbulon one question: search keywords can be defined with different tokenizers. Do you consider this in the implementation? Or how does that work with the csv import?

[sebbulon]

@emmenko indeed .. custom tokenisers are not supported right now by this PR

[emmenko]

So how is this going to work?

[PhilippSpo]

@sebbulon There are no tests for updating existing search keywords, right?

[sebbulon]

@emmenko I didn't really change anything there as you can see. The CSV import already supported search keyword export to some extend, I added Search Keyword import - there was only one little change necessary.
When you create the product you need to select the tokeniser.
If you create the product with this tool right now, it will use default tokeniser - which seems to be not white space, which is not ideal I have to admit.

I guess we need to make this clear in the documentation + have another change request to support the different tokenisers.

[sebbulon]

@PhilippSpo right tests are not complete

[sebbulon]

@emmenko to answer your question - the ususal case how people use this is to tokenise the search keywords already. If they are provided separated by semicolon (or whatever the secondary delimiter is), it will be imported into separate text elements, each of them being a different token. So they technically don't need a whitespace tokeniser.
Of course we need to add the support later down the line though to support the complete feature.

I will add this to the readme

[PhilippSpo]

OK we can merge this in my opinion.
Later on we also need to add support for only updating search keywords of a specific language, since this is a frequent use case. The problem here is, that there is no update action for only updating the searchKeywords of one language. Thus we would need to enrich the action with the current search keywords before sending the update action..