[MGNLUI-1951] Queries should use JCR 2.0 bind variable mechanism Created: 23/Aug/13  Updated: 09/Mar/21  Resolved: 09/Mar/21

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 5.1
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Federico Grilli Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLUI-107 As a user I can filter in lists and t... Closed
relation
is related to MGNLUI-1950 Search on nodes whose name begins wit... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Story Points: 8

 Description   

See http://www.day.com/specs/jcr/2.0/6_Query.html#6.9.6%20Bind%20Variables
That should solve the problem of escaping invalid query terms in a more elegant way than we do now, even though it might not be so straightforward to fit it in our current way of building queries in the list and search views.


Generated at Mon Feb 12 08:51:44 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.