[MGNLREST-122] Support additive filters via multiple query-params Created: 05/Oct/17  Updated: 31/Oct/17  Resolved: 27/Oct/17

Status: Closed
Project: Magnolia REST Framework
Component/s: None
Affects Version/s: None
Fix Version/s: 2.0

Type: New Feature Priority: Neutral
Reporter: Hieu Nguyen Duc Assignee: Hieu Nguyen Duc
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 1d 7.5h
Time Spent: 1d 0.5h
Original Estimate: 3d

Issue Links:
Relates
relates to MGNLREST-120 Implement filtering operators Closed
Template:
Acceptance criteria:
Empty
Date of First Response:
Epic Link: REST Queries
Sprint: Saigon 118, Saigon 119
Story Points: 5

 Description   

Currently we have draft/experimental/undocumented support for multi-value filtering (or values separated by pipes)

+ http://<host>/.rest/delivery/tours/v1?destination=xxx|yyy
-> destination = xxx OR destination = yyy

Syntax to be refined in a follow-up discussion/ticket, before we formally document it.

—But we also want to support additive multi-value filtering, even in current draft implementation.

+ http://<host>/.rest/delivery/tours/v1?destination=xxx&destination=yyy
-> destination = xxx AND destination = yyy



 Comments   
Comment by Dai Ha [ 30/Oct/17 ]

verify with build magnolia-enterprise-pro-demo-bundle-5.6-20171029.233322-189-tomcat-bundle.zip.

Generated at Mon Feb 12 06:56:49 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.