Custom Query (2152 matches)
Results (2101 - 2103 of 2152)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#1495 | fixed | API call for getting a user's public activity stream | kindly | seanh |
Description |
An API call that returns a user's public activity stream in JSON format. |
|||
#1663 | fixed | API call for creating an activity streams event | seanh | seanh |
Description |
The create_activity() logic function already exists, but validation and authorization need to be added before it's hooked up to an API call. |
|||
#377 | wontfix | API Should return JSON in all cases | glen@… | |
Description |
When the API returns any response it should always retunr JSON. For example a 404 response should return something like {'status': 404, 'message': 'package somename not found'} When errors are encountered when creating a package: {'status': nnn, 'message': 'Validation Errors', 'errors':['description':'name cannot be blank', 'description':'license code must be an integer']} Not authorised: {'status': 503, 'message': 'You are not authorised to create this package.'} The reason being that screeds of html coming back in the response just makes it harder to debug and understand. Having the proper error codes/messages means that you can see why your package was not created. |
Note: See TracQuery
for help on using queries.