Return a "Bad Request" status if a schedule references an unknown recurrence rule

When an unknown recurrence rule is used to create a schedule, the result is an exception that is logged.

A "400 Bad Request" should be returned instead to inform the user/dashboard that the schedule cannot be created because the recurrence rules is not supported.

changed milestone to %1.0-alpha3 — Playful Platypus

added P1 + 1 deleted label

assigned to @eigenwijsje

marked this issue as related to #181 (closed)

marked this issue as related to #180 (closed)

removed the relation with #180 (closed)

marked this issue as related to #182 (closed)

changed title from Return a "Bad Request" status when a schedule is created with an unknown recurrence rule to Return a "Bad Request" status if a schedule references an unknown recurrence rule

When the rruleId is unknown, the response is now:

HTTP/1.1 400 Bad Request
Allow: GET, POST, HEAD, OPTIONS
Connection: keep-alive
Content-Type: application/json
Date: Tue, 21 Nov 2023 19:42:26 GMT
Server: nginx/1.25.2
Transfer-Encoding: chunked
Vary: Accept, origin

{
    "rruleId": [
        "Ungültige rrule - Object existiert nicht."
    ]
}

closed

{
    "rruleId": "RRule matching query does not exist."
}