08 Feb, 2013
1 commit
07 Feb, 2013
3 commits
06 Feb, 2013
6 commits
-
If a note is created with a POST request via API (`/projects/:id/notes`) status code 400 is returned instead of 404. The resource itself exists but the request is incomplete. Specs added to check different status codes when accessing, creating and updating notes.
-
If a milestone is created via API but no title given then status code 400 (Bad request) is returned instead of 404. A small helper method handles the errors collection of a milestone.
-
Creating a comment to an existing merge request via API without providing a note returns a status code 400 now, suggesting a bad request. The reason for this is the resource itself (MR) exists but the required property is not set.
-
Using the API library to create or update a merge request at the moment a 404 error is returned. This is fine when the merge request in question does not exist, but does not provide good information that for example a required attribute is missing. A status code of 400 (Bad request) is returned when creating or updating a merge request when either `source_branch` or `target_branch` is missing. A status code of 409 is returned when `source_branch` and `target_branch` are the same. Tests are added for these cases.
-
Add groups api
05 Feb, 2013
6 commits
04 Feb, 2013
4 commits
03 Feb, 2013
1 commit
01 Feb, 2013
7 commits
-
Don't setuid the repositories on installation
-
The attempt to revoke project access for a user that was not member of the project results in a 500 Internal Server error where it actually should result in a 200 OK since after the operation, the user is not member of the project. This turns the operation into an idempotent call that can be repeated with no ill effects. Updated the spec and changed the code accordingly. However, the result differs slightly, as we can't return the users project access level if the user was not member. I'm not aware if anybody relies on the result of this call. Fixes #2832
-
In case we rescue from a fatal error, we want the error and the backtrace to the error logged, so we can debug later on. This change injects the configured logger from the rails app to the grape API and logs error as well as backtrace in a rails-like fashion.
31 Jan, 2013
6 commits
-
Added methods to protect and unprotect branches in from the API
-
… bladealslayer-extend_user_api Conflicts: spec/requests/api/users_spec.rb
-
Fix bug of network graph(#2847) and trivial code clean up.
30 Jan, 2013
4 commits
-
Expose MergeRequest object as a notable in the API to allow for easy ret...
-
Improve overlap of lines in network graph
29 Jan, 2013
2 commits
-
This rescues all errors and returns a proper JSON response. Fixes #2833.
