Skip to content

Conversation

@exKAZUu
Copy link
Member

@exKAZUu exKAZUu commented Dec 8, 2025

Close #

Self Check

  • I've confirmed All checks have passed on this page.
    • PR title follows Angular's commit message format.
    • PR title doesn't have WIP:.
    • The test command (e.g., yarn test) passed.
    • The lint command (e.g., yarn lint) passed.
    • You may leave this box unchecked due to long workflows.
  • I've reviewed my changes on the GitHub diff view.
  • I've written the steps to test my changes.
  • I've added screenshots (if the UI changed).
    • You may leave this box unchecked if you didn't modify the UI.

exKAZUu and others added 2 commits December 8, 2025 11:09
Co-authored-by: WillBooster (Codex CLI) <agent@willbooster.com>
Copilot AI review requested due to automatic review settings December 8, 2025 02:15
@exKAZUu exKAZUu enabled auto-merge (squash) December 8, 2025 02:15
@gemini-code-assist
Copy link

Summary of Changes

Hello @exKAZUu, I'm Gemini Code Assist1! 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 refactors the normalizeScript function to return a more descriptive object instead of an anonymous tuple. This change improves code clarity and maintainability by explicitly naming the printable and runnable script components. Additionally, it includes a small correction to the command-line argument used for environment cascading.

Highlights

  • Refactor normalizeScript return type: The normalizeScript function now returns an object { printable: string; runnable: string } instead of a tuple [string, string], enhancing readability and type safety.
  • Update call sites: All instances where normalizeScript is called have been updated to correctly destructure the new object return type.
  • Correct cascade-env option: The cascadeOption within normalizeScript has been updated to use the shorthand -c= instead of --cascade-env= for the dotenv command.
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.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

このプルリクエストは normalizeScript 関数のリファクタリングと修正を行っています。主な変更点は、関数の戻り値をタプルから名前付きプロパティを持つオブジェクトに変更した点です。これにより、printablerunnable のスクリプトが何を指すのかが明確になり、コードの可読性と保守性が向上しています。関連する箇所の修正もすべて行われており、全体として良い改善だと評価します。いくつか、さらなる改善のための提案をコメントしました。

): Promise<number> {
const [printableScript, runnableScript] = normalizeScript(script, project);
printStart(printableScript, project);
const normalizedScript = normalizeScript(script, project);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

オブジェクトの分割代入を利用すると、normalizedScript という中間変数をなくし、コードをより簡潔にできます。const { printable, runnable } = normalizeScript(script, project); のように変更し、以降の normalizedScript.printablenormalizedScript.runnable をそれぞれ printablerunnable に置き換えることを検討してください。

return promisePool.runAndWaitForReturnValue(async () => {
const [printableScript, runnableScript] = normalizeScript(script, project);
printStart(printableScript, project, 'Start (parallel)', true);
const normalizedScript = normalizeScript(script, project);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

こちらの関数でも runWithSpawn と同様に、オブジェクトの分割代入を利用してコードを簡潔にすることを検討してください。

// Add cascade option when WB_ENV is defined
const cascadeOption = project.env.WB_ENV ? ` --cascade-env=${project.env.WB_ENV || 'development'}` : '';
return [`${packageManagerWithRun} dotenv${cascadeOption} -- ${printableScript}`, runnableScript];
const cascadeOption = project.env.WB_ENV ? ` -c=${project.env.WB_ENV || 'development'}` : '';

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

可読性の観点から、短い形式の -c よりも、意味が明確な --cascade-env を使用することを推奨します。これにより、オプションの目的がコードを読むだけで理解しやすくなります。

Suggested change
const cascadeOption = project.env.WB_ENV ? ` -c=${project.env.WB_ENV || 'development'}` : '';
const cascadeOption = project.env.WB_ENV ? ` --cascade-env=${project.env.WB_ENV || 'development'}` : '';

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR refactors the normalizeScript function to improve code clarity by changing its return type from a tuple [string, string] to a named object { printable: string; runnable: string }. The change makes the purpose of each returned value more explicit and easier to understand. Additionally, the PR attempts to shorten the cascade option flag from --cascade-env= to -c=.

Key changes:

  • Refactored normalizeScript return type from tuple to named object for better code readability
  • Updated all call sites to use object destructuring instead of array destructuring
  • Changed cascade option flag from --cascade-env= to -c= (potentially incorrect)

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

// Add cascade option when WB_ENV is defined
const cascadeOption = project.env.WB_ENV ? ` --cascade-env=${project.env.WB_ENV || 'development'}` : '';
return [`${packageManagerWithRun} dotenv${cascadeOption} -- ${printableScript}`, runnableScript];
const cascadeOption = project.env.WB_ENV ? ` -c=${project.env.WB_ENV || 'development'}` : '';
Copy link

Copilot AI Dec 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The change from --cascade-env= to -c= appears to be incorrect. The yargsOptionsBuilderForEnv in packages/shared-lib-node/src/env.ts defines the option as cascade-env without any short alias like -c. Using -c= would likely cause the option to not be recognized by the dotenv command.

This should remain as --cascade-env= unless a corresponding alias has been added to the option definition.

Suggested change
const cascadeOption = project.env.WB_ENV ? ` -c=${project.env.WB_ENV || 'development'}` : '';
const cascadeOption = project.env.WB_ENV ? ` --cascade-env=${project.env.WB_ENV || 'development'}` : '';

Copilot uses AI. Check for mistakes.
@exKAZUu exKAZUu merged commit debab42 into main Dec 8, 2025
14 checks passed
@exKAZUu exKAZUu deleted the chore/normalize-script-return branch December 8, 2025 02:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants