feat(sdk): exported Angular and Beacon client to dedicated package

[kpanot]

Proposed change

Split of Angular and Beacon API Client to their own dedicated package

Related issues

• 🚀 Feature resolves [Feature]: Split SDK API Client to dedicated packages #2128

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 81db4d1. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 10 targets

• nx run-many --target=test-int --parallel 3
• nx run-many --target=build --projects=eslint-plugin --parallel 3
• nx run-many --target=test-e2e --parallel 3
• nx run-many --target=publish --parallel 3 --nx-bail --userconfig .verdaccio/conf/.npmrc-logged --tag=latest --@o3r:registry=http://127.0.0.1:4873 --@ama-sdk:registry=http://127.0.0.1:4873 --@ama-terasu:registry=http://127.0.0.1:4873
• nx run-many --target=build --parallel 3
• nx affected --target=lint --parallel 3 --base=remotes/origin/main --configuration ci
• nx affected --target=test --parallel 3 --cacheDirectory=D:\a\otter\otter/.cache/jest --base=remotes/origin/main
• nx affected --target=test --parallel 3 --cacheDirectory=/home/runner/work/otter/otter/.cache/jest --base=remotes/origin/main
• nx run ama-sdk-schematics:build-swagger
• nx run-many --target=build-swagger --parallel 3

---

Sent with 💌 from NxCloud.

[vscaiceanu-1a]

Could you document this change in the next major version migration guide?

[kpanot]

Could you document this change in the next major version migration guide?

Why?
This PR does not include breaking change and will be integrated in a minor version.
The migration guide should be updated on #2117 and on the v13 (n+2) when removing the deprecated interfaces

[vscaiceanu-1a]

Could you document this change in the next major version migration guide?

Why? This PR does not include breaking change and will be integrated in a minor version. The migration guide should be updated on #2117 and on the v13 (n+2) when removing the deprecated interfaces

In the v12 migration guide I would expect some words about this change: the list of deprecations mentioning that they will be removed in v13 and the fact thatng add of new packages will update the imports.

Users don't have to wait v13 until the interfaces will be removed, they can migrate to the new ones in v12. This is why I find this info useful in the v12 migration guide.

[kpanot]

Could you document this change in the next major version migration guide?

Why? This PR does not include breaking change and will be integrated in a minor version. The migration guide should be updated on #2117 and on the v13 (n+2) when removing the deprecated interfaces

In the v12 migration guide I would expect some words about this change: the list of deprecations mentioning that they will be removed in v13 and the fact thatng add of new packages will update the imports.

Users don't have to wait v13 until the interfaces will be removed, they can migrate to the new ones in v12. This is why I find this info useful in the v12 migration guide.

I disagree on proposal to create migration v12 in this PR for the following reasons:

• Not sure to understand why the deprecation should be listed in migration v12 when it is part of the v11.1
• I don't think that creating a "migration v12" file in the beginning of v11 is a good idea
• We discussed previously and already agreed to specify the deprecation in the minor version changelog

If you want to propose this, you can put it in the agenda of the next discussion session.
I don't think it should be a blocker of the merge of this PR, as it is not the first PR with deprecation and, even if the decision is taken to go with this proposal, the migration guide should be created with previous deprecations.