Hannes Papenberg

Because it's not only the stemmer. This setting selects which language to use for indexing the content. That selection both influences how the text is tokenised as well as the...

Since this feature was broken in J3, there is no b/c to be broken. Besides the fact that our b/c claims don't actually extend to components and a major version...

I've changed the basebranch to 4.3-dev, since we wont be merging this into 4.2.

Going to close this PR. I'm not convinced about my own code here...

#38650 adds options to set if a custom field should be indexed as text or taxonomy or none.

> I would like to merge this in to j5 do we already have documentation? No, I need to write the complete documentation for Smart Search still.

I'm sorry to bother you with this again @Denitz, but could you fix the codestyle issues in this PR?

https://github.com/phpstan/phpstan/issues/10936

The PR in question is #9896. Even looking at the PR, I can't understand why this was merged. Regardless of that, the browser in question is EOL and not supported...

Yes, this "changes" behavior. It actually fixes it to be in line with what people expect. The goal is to only show the text when it contains anything. Right now...