summary:Path used to manage the items of _the_ agenda.
description:""
get:
responses:
"200":
content:
application/json:
schema:
type:array
items:
$ref:"#/components/schemas/AgendaItem"
description:Successful response, returns a list of items
operationId:getTheAgendaItems
summary:List all items on the agenda
description:|
This returns all items currently on the agenda for a Fachschaftssitzung. The items are directly sourced from the todo tool _Taiga_ ([fsco.li/todo](https://fsco.li/todo)).
### Which Fachschaftssitzung?
This API does not know. It only takes whatever is currently in the column “Nächste Fachschaftssitzung” in Taiga and returns this. Depending on when the next Fachschaftssitzung is, this can mean that this path returns the items on the agenda ...
* ... of the upcoming Fachschaftssitzung
* ... of the current Fachschaftssitzung (if accessed during one)
* ... of the previous Fachschaftssitzung (if accessed immediately after one)
### What's up with the weird path?
`/agendas/-/items` seems needlessly complicated, but there is a reason for that:
<!-- TODO -->
/version:
summary:Path used to get details about the version of this application.
description:""
...
...
@@ -84,6 +115,24 @@ paths:
required:true
components:
schemas:
AgendaItem:
title:Item on an agenda
description:"Anitemonanagenda.Ithasanameandanid."
required:
-id
-name
type:object
properties:
id:
description:Id of the item, as provided by the Taiga todo tool.