Align OpenAI token params test location with test layout

[PeterDaveHello]

User description

Move openai-token-params.test.mjs from src/services/apis to tests/unit/services/apis so test files follow the same layout as other unit tests.

Update the import path after the move. This is a consistency-only change and does not alter runtime behavior.

cc #922 #924

---

PR Type

Tests

---

Description

• Move test file to align with project structure

• Update import path to reflect new test location

• Ensures consistency with other unit tests layout

---

Diagram Walkthrough

flowchart LR
  oldLoc["src/services/apis/openai-token-params.test.mjs"]
  newLoc["tests/unit/services/apis/openai-token-params.test.mjs"]
  importPath["Import path updated to src/services/apis"]
  oldLoc -- "moved to" --> newLoc
  newLoc -- "references" --> importPath

Loading

File Walkthrough

Relevant files

Tests

openai-token-params.test.mjs Update import path for relocated test file                              tests/unit/services/apis/openai-token-params.test.mjs Test file moved from src/services/apis to tests/unit/services/apis Import path updated from relative './openai-token-params.mjs' to '../../../../src/services/apis/openai-token-params.mjs' Test content remains unchanged, only location and import adjusted +1/-1

---

Summary by CodeRabbit

Release Notes

No user-visible changes in this release. This update includes internal test infrastructure maintenance with no impact to functionality or user experience.

[gemini-code-assist]

Summary of Changes

Hello @PeterDaveHello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on improving the consistency of the project's test file structure. By relocating a specific test file and updating its internal import, the change ensures that unit tests follow a standardized layout without altering any runtime behavior or functionality of the application.

Highlights

• File Relocation: The test file openai-token-params.test.mjs has been moved from src/services/apis to tests/unit/services/apis to align with the project's unit test layout.
• Import Path Update: The import path within the moved test file was updated to reflect its new location, ensuring correct module resolution.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• src/services/apis/openai-token-params.test.mjs
  • Renamed to tests/unit/services/apis/openai-token-params.test.mjs
  • Updated the relative import path for getChatCompletionsTokenParams to ../../../../src/services/apis/openai-token-params.mjs

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

---

📝 Walkthrough

Walkthrough

A test file's import path was updated to reference the source module from a deeper directory path instead of a relative local path, redirecting to the correct location in the src directory without changing test logic.

Changes

Cohort / File(s)	Summary
Import Path Update tests/unit/services/apis/openai-token-params.test.mjs	Import path for getChatCompletionsTokenParams adjusted from relative to absolute path pointing to src/services/apis/openai-token-params.mjs.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Handle GPT-5 token params by provider #922: Adds the src/services/apis/openai-token-params.mjs module and its corresponding test file that this import update is now correctly referencing.

Suggested labels

Review effort 2/5

Poem

🐰 The path was tangled, now it's straight,
A little hop through src's gate,
Import adjusted, tests aligned,
A cleaner structure, well designed! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: moving the test file to align with the test directory layout and updating the import path accordingly.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[qodo-code-review]

PR Code Suggestions ✨

No code suggestions found for the PR.

[Copilot]

Pull request overview

This PR aligns the OpenAI token parameter unit test file location with the repository’s existing unit test directory structure, keeping tests out of src/ and under tests/unit/.

Changes:

• Relocates openai-token-params.test.mjs into tests/unit/services/apis/.
• Updates the test’s import to reference the production module in src/services/apis/.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[gemini-code-assist]

Code Review

The pull request successfully relocates the openai-token-params.test.mjs file to the tests/unit/services/apis/ directory, aligning it with the project's established test structure. The import path has been correctly updated to reflect the new location. No functional changes were introduced, and the existing test logic remains sound.