From 4b724ad968579315da0f49c4ee4a462f24f9cd4f Mon Sep 17 00:00:00 2001
From: Michel Knecht <michel.knecht@proton.me>
Date: Fri, 12 Sep 2025 10:49:57 +0200
Subject: [PATCH] Add escapes to patterns to allow openapi generator to
 generate client

---
 personio-personnel-data-api-oa3.yaml | 38 ++++++++++++++--------------
 1 file changed, 19 insertions(+), 19 deletions(-)

diff --git a/personio-personnel-data-api-oa3.yaml b/personio-personnel-data-api-oa3.yaml
index 88e74da..b9316c6 100644
--- a/personio-personnel-data-api-oa3.yaml
+++ b/personio-personnel-data-api-oa3.yaml
@@ -505,7 +505,7 @@ paths:
                       example: '2020-01-31'
                       format: date
                       description: "Employee hire date. Format: \"yyyy-mm-dd\". If `status` is not provided, it will be set to `active` if the hire date is in the past, or to `onboarding` if it's in the future."
-                      pattern: ^\d{4}-\d{2}-\d{2}$
+                      pattern: /^\d{4}-\d{2}-\d{2}$/
                     weekly_working_hours:
                       type: number
                       example: 40
@@ -562,7 +562,7 @@ paths:
                   example: '2020-01-31'
                   format: date
                   description: "Employee hire date. Format: yyyy-mm-dd"
-                  pattern: ^\d{4}-\d{2}-\d{2}$
+                  pattern: /^\d{4}-\d{2}-\d{2}$/
                 "employee[weekly_working_hours]":
                   description: Employee weekly working hours
                   type: number
@@ -673,7 +673,7 @@ paths:
                       example: '2020-01-31'
                       format: date
                       description: "Employee hire date. Format: \"yyyy-mm-dd\". Update of the `hire_date` will not update employee status on its own (for that you'll need to update the `status` field)"
-                      pattern: ^\d{4}-\d{2}-\d{2}$
+                      pattern: /^\d{4}-\d{2}-\d{2}$/
                     weekly_working_hours:
                       type: number
                       example: 40
@@ -723,7 +723,7 @@ paths:
                   example: '2020-01-31'
                   format: date
                   description: "Employee hire date. Format: yyyy-mm-dd"
-                  pattern: ^\d{4}-\d{2}-\d{2}$
+                  pattern: /^\d{4}-\d{2}-\d{2}$/
                 "employee[weekly_working_hours]":
                   description: Employee weekly working hours
                   type: number
@@ -3501,25 +3501,25 @@ components:
                   example: Standard Hours
                 monday:
                   example: 08:30
-                  pattern: ^\d\d:\d\d$
+                  pattern: /^\d\d:\d\d$/
                 tuesday:
                   example: 08:30
-                  pattern: ^\d\d:\d\d$
+                  pattern: /^\d\d:\d\d$/
                 wednesday:
                   example: 08:30
-                  pattern: ^\d\d:\d\d$
+                  pattern: /^\d\d:\d\d$/
                 thursday:
                   example: 08:30
-                  pattern: ^\d\d:\d\d$
+                  pattern: /^\d\d:\d\d$/
                 friday:
                   example: 08:30
-                  pattern: ^\d\d:\d\d$
+                  pattern: /^\d\d:\d\d$/
                 saturday:
                   example: 00:00
-                  pattern: ^\d\d:\d\d$
+                  pattern: /^\d\d:\d\d$/
                 sunday:
                   example: 00:00
-                  pattern: ^\d\d:\d\d$
+                  pattern: /^\d\d:\d\d$/
         type:
           $ref: '#/components/schemas/TypeEnum'
         universal_id:
@@ -4015,12 +4015,12 @@ components:
           format: date
         start_time:
           type: string
-          pattern: ^\d\d:\d\d$
+          pattern: /^\d\d:\d\d$/
           example: "08:00"
         end_time:
           type: string
           nullable: true
-          pattern: ^\d\d:\d\d$
+          pattern: /^\d\d:\d\d$/
           example: "17:00"
         break:
           type: integer
@@ -4078,13 +4078,13 @@ components:
                 format: date
               start_time:
                 type: string
-                pattern: ^\d\d:\d\d$
+                pattern: /^\d\d:\d\d$/
                 example: "08:00"
                 description: "Format: hh:mm"
               end_time:
                 type: string
                 nullable: true
-                pattern: ^\d\d:\d\d$
+                pattern: /^\d\d:\d\d$/
                 example: "17:00"
                 description: "Format: hh:mm"
               break:
@@ -4112,13 +4112,13 @@ components:
           format: date
         start_time:
           type: string
-          pattern: ^\d\d:\d\d$
+          pattern: /^\d\d:\d\d$/
           example: "08:00"
           description: "Format: hh:mm"
         end_time:
           type: string
           nullable: true
-          pattern: ^\d\d:\d\d$
+          pattern: /^\d\d:\d\d$/
           example: "17:00"
           description: "Format: hh:mm"
         break:
@@ -4195,13 +4195,13 @@ components:
           example: '2020-01-31'
         attendances[][start_time]:
           type: string
-          pattern: ^\d\d:\d\d$
+          pattern: /^\d\d:\d\d$/
           description: "Start time. Format: hh:mm"
           example: '08:00'
         attendances[][end_time]:
           type: string
           nullable: true
-          pattern: ^\d\d:\d\d$
+          pattern: /^\d\d:\d\d$/
           description: "End time. Format: hh:mm"
           example: '12:00'
         attendances[]break: