gitlabhq/spec/requests/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
..
groups_spec.rb Add test for duplicate group paths 2013-02-01 18:58:53 +01:00
issues_spec.rb Rspec fixes 2013-01-04 18:50:31 +02:00
merge_requests_spec.rb Test added to check creation of note to a non-existent MR via API 2013-02-06 17:05:55 +01:00
milestones_spec.rb Tests added to check status codes when handling milestone via API 2013-02-06 17:11:00 +01:00
notes_spec.rb Merge branch 'master' into fixes/api 2013-02-08 10:32:42 +01:00
projects_spec.rb API: refined status code handling when adding or updating a project member 2013-02-08 14:33:29 +01:00
session_spec.rb Remove backward compatibility of factories. 2012-11-13 22:27:45 +11:00
users_spec.rb Merge branch 'extend_user_api' of https://github.com/bladealslayer/gitlabhq into bladealslayer-extend_user_api 2013-01-31 13:00:50 +02:00