Add mechanism for following openApi specifications when generating query parameters

Hi, could you please provide some kind of mechanism how to say guardrail to follow openApi specification when generating code from swagger? Specifically I am talking about **query** parameters with array type (but there could be more differences), which are handled as **multi** (userId=1,userId=2) insted of **default** comma separated values (userIds=1,2). According to specification if there is no explicit _collectionFormat_ parameter it should expect parameters in csv format. As a result guardrail will parse parameter userIds=1,2 as single value collection with value 1,2. This is quite an issue for us as we have micro services written in several languages and non scala generators are following openApi specification which leads to errors on our side.