chore: release v2.2.3 - refine code quality, boost coverage, and update documentation

[toozuuu]

🚀 Overview

This PR prepares the project for the v2.2.3 release. The primary focus was on resolving critical SonarLint/ESLint warnings, reaching the required test coverage threshold, and synchronizing project-wide metadata and documentation.

🛠️ Key Changes

1. Code Quality & Refactoring

• Material Support Overhaul: Refactored the withMaterialSupport static method in ngxsmk-datepicker.ts to resolve Cognitive Complexity (S3776) and Function Nesting (S2004) warnings.
• Static Member Safety: Marked _allInstances as readonly (SonarLint S2933).
• Cleanup: Removed redundant diagnostic assignments (_patchId) and simplified internal provider patching logic.

2. Testing & Coverage

• New Test Suite: Added lint-fix-coverage.spec.ts to provide unit test coverage for internal utility and patching methods.
• Coverage Milestone: Successfully increased function test coverage to ~68.2%, surpassing the global project threshold of 68%.

3. Project Maintenance

• Version Alignment: Updated project version to 2.2.3 across the root and library package.json files.
• Script Cleanup: Removed the redundant demo script from package.json (duplicate of start).
• File System Hygiene: Cleared temporary logs, coverage reports, and diagnostic text files.

4. Documentation Sync

• Markdown Overhaul: Synchronized 30+ Markdown files with the latest release date (March 9, 2026) and stable version reference.
• Changelog: Detailed the stability, coverage, and linting improvements in CHANGELOG.md.

✅ Verification Results

• Build: npm run build:optimized and npm run build:demo completed successfully.
• Tests: All 1,216 tests are passing.
• Lint: Main library passes linting (minor any usage in spec files remains within acceptable limits).
• Bundle: Source maps correctly removed from production build; bundle size remains optimized (~127KB).

---

Note

This release contains no breaking changes and is fully backward compatible with the v2.2.x series.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​angular/​platform-browser-dynamic@​21.0.3 ⏵ 20.3.16				+2
	@​angular-eslint/​template-parser@​20.6.0 ⏵ 20.7.0
	@​angular/​language-service@​20.3.16
	@​ionic/​angular-toolkit@​12.3.0
	@​typescript-eslint/​parser@​8.46.4 ⏵ 8.52.0				-1
	@​angular/​router@​21.0.3 ⏵ 20.3.16	-26		+1	+2
	@​capacitor/​core@​8.0.0
	@​angular-eslint/​builder@​20.6.0 ⏵ 20.7.0
	@​angular/​platform-browser@​21.0.3 ⏵ 20.3.16	-23		+1	+2
	eslint-plugin-prefer-arrow@​1.2.2
	@​types/​jasmine@​5.1.12 ⏵ 5.1.13	+25		+1	-6
	@​angular/​animations@​21.2.0 ⏵ 20.3.16			+1
	@​angular-eslint/​schematics@​20.6.0 ⏵ 20.7.0
	@​angular/​compiler-cli@​21.0.3 ⏵ 20.3.16	-19
	@​angular/​forms@​21.0.3 ⏵ 20.3.16	-21			+2
	@​angular/​cli@​21.0.2 ⏵ 20.3.14
	@​angular/​core@​21.0.3 ⏵ 20.3.16	-15	+6	+1	+2	+20
	@​angular/​compiler@​21.0.3 ⏵ 20.3.16	-14	+16	+1	+2
	@​angular/​common@​21.0.3 ⏵ 20.3.16	-2			+2	+40
	@​typescript-eslint/​eslint-plugin@​8.46.4 ⏵ 8.52.0	+1		+1	-1
	jasmine-spec-reporter@​5.0.2
	@​angular-devkit/​build-angular@​21.0.2 ⏵ 20.3.14				+2
	karma-jasmine-html-reporter@​2.1.0
	eslint-plugin-import@​2.32.0
	karma-chrome-launcher@​3.2.0
	karma-coverage@​2.2.1
	karma-jasmine@​5.1.0
	karma@​6.4.4
	eslint@​9.39.2
	ionicons@​7.4.0
	jasmine-core@​5.1.2
	eslint-plugin-jsdoc@​48.11.0
	@​capacitor/​cli@​8.0.0
See 6 more rows in the dashboard

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm entities is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: examples/ionic-test-app/package-lock.json → npm/@angular-devkit/build-angular@20.3.14 → npm/entities@4.5.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/entities@4.5.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm entities is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: examples/ionic-test-app/package-lock.json → npm/@angular-devkit/build-angular@20.3.14 → npm/entities@6.0.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/entities@6.0.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report