feat(eslint-plugin): renamed exported recommended

[kpanot]

fix(eslint-plugin): turn yaml parser really optional
deprecate(eslint-plugin): recommended exports based on types

Proposed change

feat(eslint-plugin): renamed exported recommended
fix(eslint-plugin): turn yaml parser really optional
deprecate(eslint-plugin): recommended exports based on types

Related issues

• 🚀 Feature resolves [Feature]: Split the linter plugin to multiple plugins #1487
• 🐛 Fix resolves [Bug]: several peerDeps are flagged as optional in @o3r/eslint-plugin but usage of it are exposed at the root #2482

[matthieu-crouzet]

Shouldn't we do the same ng-update for the @o3r/eslint-config-otter
as the ng-add of @o3r/eslint-plugin does nothing but @o3r/eslint-config-otter does the setup
and in @o3r/eslint-config-otter we should migrate to the not deprecated configs

Moreover do we really need this fix right now as we are working on the ESLint flat config ? or could it be done directly inside the branch for this migration to flat config ?

[kpanot]

Shouldn't we do the same ng-update for the @o3r/eslint-config-otter as the ng-add of @o3r/eslint-plugin does nothing but @o3r/eslint-config-otter does the setup and in @o3r/eslint-config-otter we should migrate to the not deprecated configs

Indeed, due to technically limitation (fake recursive ref to @o3r/schematics detected by Nx), it is simpler to do it in @o3r/eslint-config-otter.

Moreover do we really need this fix right now as we are working on the ESLint flat config ? or could it be done directly inside the branch for this migration to flat config ?

Nothing requires to have the flat config to fix the exposed recommended.
I think, in contrary, that this should not be done on the already huge linter feature branch

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 28087e4. 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 11 targets

• nx run-many --target=test-int --parallel 3
• nx affected --target=test --parallel 3 --cacheDirectory=D:\a\otter\otter/.cache/jest --base=remotes/origin/main --collectCoverage
• nx affected --target=test --parallel 3 --cacheDirectory=/home/runner/work/otter/otter/.cache/jest --base=remotes/origin/main --collectCoverage
• 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 --@o3r-training:registry=http://127.0.0.1:4873
• nx run-many --target=documentation --parallel 3
• nx run ama-sdk-schematics:build-swagger
• nx run-many --target=build --parallel 3
• nx affected --target=lint --parallel 3 --base=remotes/origin/main --configuration ci
• nx run-many --target=build-swagger --parallel 3

---

Sent with 💌 from NxCloud.

[fpaul-1A]

off is the recommended value for this rule?

[kpanot]

It is the current value.
It can be changed, in the big eslint refactor if we want

[codecov]

Codecov Report

Attention: Patch coverage is 96.15385% with 1 line in your changes missing coverage. Please review.

Project coverage is 65.87%. Comparing base (4497355) to head (28087e4).
Report is 4 commits behind head on main.

✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
...s/ng-update/v11.5/update-configs/update-configs.ts	94.11%	1 Missing ⚠️

Additional details and impacted files

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

---

🚨 Try these New Features:

• JS Bundle Analysis - Avoid shipping oversized bundles