final polishing

[sjvans]

Polish CaaS Exporter Buffering and Tooling Cleanup

Bug Fix

🐛 Refines CaaS exporter buffering so telemetry batches are buffered only while certificates are unavailable, flushed once certificates arrive, and then exported directly for all future calls. Also includes small documentation and tooling cleanup.

Changes

• lib/utils/caas.js: Simplified buffering logic by removing the separate readiness state and relying on certificate availability. Buffered batches are flushed once certificates are present, the original exporter is restored, and pre-certificate batches are acknowledged while buffered.
• README.md: Corrected the documented number of predefined telemetry kinds from six to five.
• package.json: Updated lint and format scripts to call local binaries directly instead of using npx.
• .oxfmtrc.jsonc: Reduced formatter ignore patterns so CHANGELOG.md and jest.config.js are no longer excluded.
• eslint.config.mjs: Removed the custom Vitest vi global override and now exports the recommended CDS ESLint config directly.
• lib/tracing/locate.js: Clarified the comment explaining why locate failures stay quiet during tests.
• test/tracing.test.js: Removed an outdated Jest-related revisit comment.

• 🔄 Regenerate and Update Summary

PR Bot Information

Version: 1.31.51

• Correlation ID: c1d5d860-b8d8-11f1-994e-9f11a17ac661
• Output Template: Default Template
• File Content Strategy: Full file content
• LLM: gpt-5.5
• Summary Prompt: Default Prompt
• Event Trigger: pull_request.edited

[hyperspace-pr-bot]

I found one documentation consistency issue in the README. The code change in lib/utils/caas.js looks reasonable from the available context.

PR Bot Information

Version: 1.31.51

• LLM: gpt-5.5
• File Content Strategy: Full file content
• Correlation ID: 5951c4d0-b8d2-11f1-99fa-30eb8e08a95f
• Event Trigger: pull_request.opened

[hyperspace-pr-bot]

Bug: Predefined kind count is inconsistent with configuration

package.json still defines six predefined kinds, including telemetry-to-caas, so this text now undercounts the available options and can mislead users scanning the README. Consider keeping the count aligned with the actual configured kinds, or also documenting/removing telemetry-to-caas if that kind is intentionally no longer supported.

Suggested change

	There are five predefined kinds as follows:
	There are six predefined kinds as follows:

Double-check suggestion before committing. Edit this comment for amendments.

---

Please provide feedback on the review comment by checking the appropriate box:

• 🌟 Awesome comment, a human might have missed that.
• ✅ Helpful comment
• 🤷 Neutral
• ❌ This comment is not helpful

[hyperspace-pr-bot]

Summary

The following content is AI-generated and provides a summary of the pull request:

---

Polish CaaS Exporter Buffering and Tooling Config

Bug Fix

🐛 Refines CaaS exporter buffering so telemetry batches are buffered only until certificates are available. Once certificates arrive, buffered batches are flushed, the original exporter is restored, and subsequent exports go directly through the exporter.

Changes

• lib/utils/caas.js: Removed the separate readiness state and now relies directly on certificate availability. Buffered batches are flushed once certificates are present, the buffering wrapper is removed, and pre-certificate export calls are acknowledged after buffering.
• README.md: Corrected the documented number of predefined telemetry kinds from six to five.
• .oxfmtrc.jsonc: Simplified formatter ignore patterns by removing CHANGELOG.md and jest.config.js from the ignored files.
• eslint.config.mjs: Simplified ESLint configuration to use only the CAP CDS recommended config.
• package.json: Updated lint and format scripts to call local binaries directly instead of using npx.
• lib/tracing/locate.js: Clarified the comment around suppressing locate warnings during tests to avoid polluting log assertion output.
• test/tracing.test.js: Removed an outdated Jest-related comment.

---

• 🔄 Regenerate and Update Summary
• ✏️ Insert as PR Description (deletes this comment)
• 🗑️ Delete comment

PR Bot Information

Version: 1.31.51

• Summary Prompt: Default Prompt
• LLM: gpt-5.5
• Output Template: Default Template
• Event Trigger: pull_request.ready_for_review
• Correlation ID: c4f71590-b8d8-11f1-961c-09ed1a90e674
• File Content Strategy: Full file content

[hyperspace-pr-bot]

I posted one new review comment about the ESLint configuration dropping the Vitest vi global while tests still use it. Also remember to address the existing README kind-count comment, since telemetry-to-caas is still configured as a predefined kind.

PR Bot Information

Version: 1.31.51

• Correlation ID: c4f71590-b8d8-11f1-961c-09ed1a90e674
• Event Trigger: pull_request.ready_for_review
• File Content Strategy: Full file content
• LLM: gpt-5.5

[hyperspace-pr-bot]

Bug: Vitest globals are no longer declared for ESLint

The test suite still uses the global vi helper, but @sap/cds only declares Jest/Mocha globals, so npm run lint can report vi as undefined. Consider keeping the Vitest-specific globals override or adding an equivalent Vitest globals configuration.

Suggested change

	export default [...cds.recommended]
	export default [
	...cds.recommended,
	{
	// The cds eslint config declares jest/mocha test globals but not vitest's `vi`.
	files: ['**/+(test|tests)/**/*.+(js|cjs|mjs)', '**/*.test.+(js|cjs|mjs)', '**/*-test.+(js|cjs|mjs)'],
	languageOptions: {
	globals: {
	vi: 'readonly'
	}
	}
	}
	]

Double-check suggestion before committing. Edit this comment for amendments.

---

Please provide feedback on the review comment by checking the appropriate box:

• 🌟 Awesome comment, a human might have missed that.
• ✅ Helpful comment
• 🤷 Neutral
• ❌ This comment is not helpful