Closed Bug 848256 Opened 11 years ago Closed 11 years ago

Phonebook :: API :: When request have comma separated parameters, API does not get the data.

Categories

(Participation Infrastructure :: Phonebook, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED
2013-09-12

People

(Reporter: ravi, Assigned: giorgos)

References

Details

(Whiteboard: [kb=1098890] )

User Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.56 Safari/537.17

Steps to reproduce:

1. Hit the API request with these argumetns -- https://mozillians.allizom.org/api/v1/users/?app_name=mozapp&app_key=test&groups=staff,qa

2. Observe for the response.


Actual results:

The response code was 200. The result had nothing in it.


Expected results:

Should be able to fetch the results with comma separated parameters.
Confirmed. Thanks for reporting Ravi!
Status: UNCONFIRMED → NEW
Ever confirmed: true
Assignee: nobody → giorgos
Status: NEW → ASSIGNED
Whiteboard: [kb=1098890]
Depends on: 911980
Commit pushed to master at https://github.com/mozilla/mozillians

https://github.com/mozilla/mozillians/commit/a814dc7f4b5a7157d6514ee0ced0e2e0f5fb63d9
[fix bug 911980][fix bug 848256][fix bug 848257] API refactoring, tests and bug fixing.

* Refactor API to not use the ElasticSearch backend (bug 911980)
* Explicitly set the fields returned by UserResource
* Fix filters containing spaces (bug 848257)
* Fix filters with commas (bug 848256)
* Fix default data ordering (bug 914384)
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2013-09-12
The URL above shows 546 accounts, which is better than a blank screen. Furthermore, 546 is the sum of the members in the QA group (https://mozillians.allizom.org/api/v1/users/?app_name=mozapp&app_key=test&groups=qa) and the staff group (https://mozillians.allizom.org/api/v1/users/?app_name=mozapp&app_key=test&groups=staff), which suggests that the comma is doing what it's supposed to.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.