DeepL glossary missing Arabic as source and target language

The language Arabic is not supported by the API for now.
Available languages are listed here: https://developers.deepl.com/docs/api-reference/glossaries/openapi-spec-...

Once the language is available via the API, i'll update the tmgmt_deepl_glossary submodule.

I made a GET request to the https://api.deepl.com/v2/glossary-language-pairs endpoint. While the response included multiple language pairs, I'm only including the English to Arabic pair:
{
"supported_languages": [
{
"source_lang": "en",
"target_lang": "ar"
}
]
}
Thank you for looking at this. :)

Thank you once again for taking care of this, but the merge failed due to phpcs and phpstans :(

@sachit.thapa: The tests for phpstan (next minor) won't be fixed for the 2.2.x release.
Those are handled in 2.3.x - were all pipelines are green.

It would be great, if you could test the Merge Request with version 2.2.x on you projects and provide feedback. Afterward i'll integrate the feature into 2.3.x.

@steffenr, ! I've downloaded and tested MR !39 in my environment using version 2.2.x. I was able to see Arabic in both the source and target language as expected. I uploaded the glossary via Postman using the API endpoints, and everything worked smoothly without the issues I encountered earlier. I also tested editing and saving through Drupal, and it produced the expected results. Looks good on my end! Thanks

I just had a look at related issues, which would be affected by the Merge Request.
I have to make some more changes to the selection of languages, since custom langcodes, which are mapped in the translator configuration won't show up.

Automatically closed - issue fixed for 2 weeks with no activity.