move GET /localization response object to schemas

[orolhawion]

When generating code from OpenApi spec files some generators cannot handle inline schemas properly. In this specific case the generator I use does not generate an enum as stated in the spec but simply a string. The content-type is defined as json, but generated client methods just return a string, where the Api returns a Json string, (pract vs. "pract"), which makes it more difficult and error-prone to properly evaluate the Api response.

Moving the enum to schemas avoids this issue. Please consider accepting this PR.

Kind regards,
Martin

[gem-uhe]

I informed the gematik TIM Team about this PR. They will add this topic to the agenda of the next TIM meeting with the TIM providers and manufacturers.

[ichderjens]

Hello,

can u give us some details on the generator in use?
The API endpoint was quite useful for the TI-M 1.1.2 permission management, which we changed for TI-M Pro and ePA.
Based on that we would suggest to delete the API endpoint. Do you really need it for your development purpose?

[orolhawion]

Hi,

sorry for the late answer. We used the Kotlin generator with a Spring Boot lib, but you are right, in the meantime the API became obsolete. However, please consider to avoid using inline schemas because it may interfere with proper code generation.

Regards
Martin