PMT-4: Mitarbeiter zu einem projekt hinzufügen #14
1 changed files with 40 additions and 1 deletions
41
api/pmt.yml
41
api/pmt.yml
|
@ -68,6 +68,15 @@ components:
|
|||
plannedEnd:
|
||||
type: string
|
||||
format: date-time
|
||||
AddEmployeeDTO:
|
||||
type: object
|
||||
properties:
|
||||
employeeId:
|
||||
type: integer
|
||||
format: int64
|
||||
qualificationId:
|
||||
type: integer
|
||||
format: int64
|
||||
responses:
|
||||
Unauthorized:
|
||||
description: "Unauthorized"
|
||||
|
@ -147,6 +156,37 @@ paths:
|
|||
|
||||
|
||||
/project/{id}:
|
||||
post:
|
||||
operationId: "addEmployee"
|
||||
description: "Adds an employee to a specific Project"
|
||||
parameters:
|
||||
- in: path
|
||||
name: id
|
||||
schema:
|
||||
type: integer
|
||||
format: int64
|
||||
required: true
|
||||
requestBody:
|
||||
content:
|
||||
application/json:
|
||||
schema:
|
||||
$ref: "#/components/schemas/AddEmployeeDTO"
|
||||
responses:
|
||||
204:
|
||||
description: "Employee successfully added to the specific Project"
|
||||
401:
|
||||
$ref: "#/components/responses/Unauthorized"
|
||||
404:
|
||||
$ref: "#/components/responses/NotFound"
|
||||
409:
|
||||
$ref: "#/components/responses/Conflict"
|
||||
422:
|
||||
$ref: "#/components/responses/UnprocessableContent"
|
||||
500:
|
||||
$ref: "#/components/responses/InternalError"
|
||||
503:
|
||||
SZUT-Rajbir marked this conversation as resolved
Outdated
|
||||
$ref: "#/components/responses/ServiceUnavailable"
|
||||
|
||||
delete:
|
||||
operationId: "deleteProject"
|
||||
description: "Delete a specific Project"
|
||||
|
@ -170,4 +210,3 @@ paths:
|
|||
type: string
|
||||
500:
|
||||
$ref: "#/components/responses/InternalError"
|
||||
SZUT-Rajbir marked this conversation as resolved
Outdated
SZUT-Dominik
commented
Newline bitte wieder an das Ende tuhen. Newline bitte wieder an das Ende tuhen.
|
||||
|
||||
|
|
Loading…
Reference in a new issue
Ich habe nochmal nachgeschaut, ein Not Acceptable ist was anderes und hat mit der Browser aushandlung vom Content Format zu tuhen.
wir wollen statdessen einen 422 Unprocessable Content schmeisen (der Schema eintrag exestiert bereits, den hier verlinkten aber bitte löschen)