52e57e70fd
Add documentation for issue #16602 After discussing with the team (Thomas), https://discord.com/channels/1130383047699738754/1443986309436936212 we decided that updating the documentation. The issue is In compute-where-condition-parts.ts, the like/ilike cases pass values directly to SQL without adding % wildcards for api using, so they behave like exact matches. This PR updates the documentation regarding the use of `like`, `ilike` and `containsIlike` filters. Instead of auto-wrapping values with % wildcards in the backend, we are choosing to leave the control to the API users (%value% or value%). <img width="651" height="409" alt="image" src="https://github.com/user-attachments/assets/b3537af6-a0b0-4fff-a86d-a9ae334d628e" /> But I add wildcard for `startsWith` and `endsWith` because these operators have a fixed semantic meaning. (To see the results, please refresh the cache first, then restart the server.） <img width="878" height="458" alt="image" src="https://github.com/user-attachments/assets/ab0f4e7c-df50-45ef-b1c8-e43c8881a9a3" /><img width="482" height="288" alt="image" src="https://github.com/user-attachments/assets/20dc39ee-2417-4ecc-810e-ea0ead33d803" /> --------- Co-authored-by: Thomas Trompette <thomas.trompette@sfr.fr>