04 Jun, 2013
1 commit
-
Conflicts: Gemfile.lock app/models/ability.rb app/models/project.rb app/views/snippets/_form.html.haml db/schema.rb features/steps/shared/paths.rb spec/factories.rb spec/models/project_spec.rb
03 Jun, 2013
2 commits
-
… if it exist in other owned project
23 May, 2013
1 commit
14 May, 2013
1 commit
07 May, 2013
1 commit
06 May, 2013
1 commit
03 Apr, 2013
1 commit
01 Apr, 2013
1 commit
-
Also specify separate project factory for project with filled repo
25 Mar, 2013
1 commit
18 Mar, 2013
1 commit
07 Mar, 2013
2 commits
-
Conflicts: doc/api/projects.md spec/requests/api/projects_spec.rb
06 Mar, 2013
1 commit
-
Additional Admin APIs
05 Mar, 2013
5 commits
-
Conflicts: lib/api/projects.rb
01 Mar, 2013
2 commits
-
This allows you to set the namespace ID for projects via the the API. By default it is created for the current user. You can assign it to the global namespace by passing `GLN` which translates to 'Global Namespace'.
27 Feb, 2013
6 commits
-
Added a helper method to check if required parameters are given in an API call. Can be used to return a `400 Bad Request` return code if a required attribute is missing. Code clean up and fixed tests.
-
closes #2300
-
The API documentation of repository is updated and now contains infos to status codes. Code documentation is also adjusted for `GET /projects/:id/repository/commits` and includes infos to pagination attributes. Tests are updated.
20 Feb, 2013
3 commits
-
Conflicts: spec/requests/api/projects_spec.rb
-
Conflicts: spec/requests/api/projects_spec.rb
16 Feb, 2013
1 commit
-
When a user is not authorized to see the list of hooks for a project, he is still able to access the hooks separately. For example if access to `GET /projects/:id/hooks` fails and returns a `403 Unauthorized` error it is still possible to access a hook directly via `GET /projects/:id/hooks/:hook_id`. Fixes access, also added tests to check access and status codes of hooks.
14 Feb, 2013
2 commits
-
Status code 422 (Unprocessable Entity) returned if invalid url is given when creating or updating a project hook.
-
When the project limit is reached the user is not allowed to create new ones. Instead of error code 404 the status code 403 (Forbidden) is returned with error message via API.
13 Feb, 2013
4 commits
-
Extracted a method for 400 error (Bad request) and adjusted code accordingly. The name of the missing attribute is used to show which one was missing from the request. It is used to give an appropriate message in the json response.
-
When using project snippets via API the functions now provide status codes for different situations other then only returning 404 error. If required parameters are missing, e.g. `title` when creating a project snippet a 400 (Bad request) error is returned. The snippet delete function now is idempotent and returns a 200 (Ok) regardless if the snippet with the given id is available or not. Changing return codes of these functions has the advantage that the 404 error is used only for resources, which are not available. Tests added to check these status codes when handling project snippets.
12 Feb, 2013
1 commit
-
Different status codes in the API lib are returned on hook creation, update or deletion. If a required parameter is not given (e.g. `url` in `/projects/:id/hooks/:hook_id`) status code 400 (Bad request) is returned. On hook deletion a 200 status code is returned, regardless if the hook is present or not. This makes the DELETE function an idempotent operation. Appropriate tests are added to check these status codes.
09 Feb, 2013
1 commit
-
Instead of using funtion `error!` the function `not_found!` is used to return 404 error. Adjusted documentation accordingly.
08 Feb, 2013
1 commit
-
Accessing a repository branch that does not exist returns a 404 error instead of 200 now. Added a test.