Migrate to 12.0 🐫

[ivy-rew]

A friendly conversion provided by market-up2date-keeper 🤖 🤝

[github-actions]

Test Results

2 tests   2 ✅  14s ⏱️
1 suites  0 💤
1 files    0 ❌

Results for commit 2629ddb.

[github-actions]

Test Results

2 tests   2 ✅  15s ⏱️
1 suites  0 💤
1 files    0 ❌

Results for commit 2629ddb.

♻️ This comment has been updated with latest results.

[nqhoan-axonivy]

[WAIT] Contacted Thomas already but still cannot get an accesskey for DeepL API testing
=> Next action: Discuss with Alex Scharping to create a new account => need a credit card

[ivy-rew]

[WAIT] Contacted Thomas already but still cannot get an accesskey for DeepL API testing => Next action: Discuss with Alex Scharping to create a new account => need a credit card

IMHO we could also migrate the project to 12 without actually testing the compliance with the real life API of deepL.
We have a mock service in test project which we can use to simulate the real execution ... with it we can verify the functionality of the connector and demo.

By example: go to your Designer install directory, navigate into the configuration dir, create an app.yaml file and put in the following contents.

# yaml-language-server: $schema=https://json-schema.axonivy.com/app/12.0.0/app.json
RestClients:
  deepl:
    Url: '{ivy.app.baseurl}/api/mock'
    Properties:
      AUTH.deepLKey: notMyKey
    Features:
    - ch.ivyteam.ivy.rest.client.mapper.JsonFeature
    - org.glassfish.jersey.media.multipart.MultiPartFeature
    - ch.ivyteam.ivy.rest.client.security.CsrfHeaderFeature

With this the Designer will fire against the local mock backend, rather than the real deepl endpoints. Through this you can test the whole project for its compatibility to version 12.

[ivy-rew]

I'll document this app.yaml development approach in readme @nqhoan-axonivy

[nqhoan-axonivy]

Hurray... got it. so let me go to next step

[nqhoan-axonivy]

LGTM