gitlabhq/lib/api
Sebastian Ziebell 818caf0b5d API: refined status code handling when adding or updating a project member
When a user is added to a project that is already a member of, a status code 201 is now returned to
signal an idempotent operation. If something fails then instead of returning error code 404 different
more specific error codes are returned. Status code 400 (Bad request) is returned when a required
attribute, e.g. `access_level` is not given or 422 if there is a semantic error, e.g. should
the `access_level` have an unsupported value.

Specs are added to check these status codes.
2013-02-08 14:33:29 +01:00
..
entities.rb Code deduplication using inheritance for GroupDetail 2013-02-03 19:38:33 +01:00
groups.rb Fix groups api: differ between users and admin 2013-02-01 15:00:12 +01:00
helpers.rb Fix namespace api autocomplete 2012-12-12 12:54:28 +02:00
internal.rb deploy keys support for gitlab-shell api 2013-02-07 09:56:13 +02:00
issues.rb Fixed missing current user for issue observer 2013-01-02 20:25:25 +02:00
merge_requests.rb Creating MR comment without a note returns status code 400 (Bad request) 2013-02-06 17:02:30 +01:00
milestones.rb Status code 400 returned if title not given in a milestone (via API) 2013-02-06 17:10:29 +01:00
notes.rb Merge branch 'master' into fixes/api 2013-02-08 10:32:42 +01:00
projects.rb API: refined status code handling when adding or updating a project member 2013-02-08 14:33:29 +01:00
session.rb API: return 401 for invalid session 2012-09-20 08:38:08 -07:00
users.rb Extended users API to support updating and deleting users. 2012-12-18 21:24:31 +02:00