feat: o3r pipeline

[vscaiceanu-1a]

Proposed change

Related issues

• 🚀 Feature [Feature] Generate workspace with CI/CD capacity #689

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 612fcf2. 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=test-e2e --parallel 3
• nx run-many --target=build --projects=eslint-plugin --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 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-many --target=build --parallel 3
• nx run ama-sdk-schematics:build-swagger
• nx affected --target=lint --parallel 3 --base=remotes/origin/main --configuration ci
• nx run-many --target=build-swagger --parallel 3

---

Sent with 💌 from NxCloud.

[sdo-1A]

do you need to specify | undefined if you use ? at the end of the variable name?

[vscaiceanu-1a]

back in the day we had an issue:

interface I {
  a?: string;
}

// valid:
const v1: I = {};

// invalid:
const v2: I = { a: undefined };

but with explicit undefined:

interface I {
  a?: string | undefined;
}

// valid:
const v1: I = {};
const v2: I = { a: undefined };