Thomas Sigdestad

Well.. Even if it was not modified? Also "published.last" is not a good name imho. Maybe "publish.time" makes more sense?

Maybe solution is a "touch" date in metadata, similar to how its done with files?

@rymsha something is obviously not working as expected. Could we arrange a meeting to clarify things related to stemming for med and CWE?

So, includeInAllText just indicates if a property should be included when creating the _allText "virtual field". What we need is that _allText get's stemmed.

But doesn't content API use node API directly? How can it do something else than what node api supports?

Basically, what I would like to know is how to specify that -_allText should be stemmed?

Ok, so we basically need to define a proper solution for this in the node API, implement and document it. There is at least one known "problem" with this in...

this -> There is no way of specifying stemming for _allText via node API import/export -> currently uses an undocumented obscure format for transferring stemming info (at least for _allText)...

FYI guys. We (me and PMI) tried to remove this earlier, and it caused havoc in the Next.js project, so this has to be verified carefully before going live. In...

OFC, textcomponent should ideally not be used for headless approaches.