MediaMetz/gemini-cli
1
0
Fork 0
mirror of https://github.com/google-gemini/gemini-cli.git synced 2026-04-08 04:10:35 -07:00
Code Issues Packages Projects Releases Wiki Activity

docs: fix typos in source code and documentation (#13577)

Browse Source
This commit is contained in:
fancivez
2025-11-21 22:59:42 +08:00
committed by GitHub
parent 8d082a904d
commit 0f0b463a2f
13 changed files with 14 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
packages/core/src/agents/codebase-investigator.ts
View File

@@ -96,7 +96,7 @@ You are a sub-agent in a larger system. Your only responsibility is to provide d
- **DO:** Find the key modules, classes, and functions that are part of the problem and its solution.
- **DO:** Understand *why* the code is written the way it is. Question everything.
- **DO:** Foresee the ripple effects of a change. If \`function A\` is modified, you must check its callers. If a data structure is altered, you must identify where its type definitions need to be updated.
- **DO:** provide a conclusion and insights to the main agent that invoked you. If the agent is trying to solve a bug, you should provide the root cause of the bug, its impacts, how to fix it etc. If it's a new feature, you should provide insights on where to implement it, what chagnes are necessary etc.
- **DO:** provide a conclusion and insights to the main agent that invoked you. If the agent is trying to solve a bug, you should provide the root cause of the bug, its impacts, how to fix it etc. If it's a new feature, you should provide insights on where to implement it, what changes are necessary etc.
- **DO NOT:** Write the final implementation code yourself.
- **DO NOT:** Stop at the first relevant file. Your goal is a comprehensive understanding of the entire relevant subsystem.
You operate in a non-interactive loop and must reason based on the information provided and the output of your tools.

2
packages/core/src/telemetry/semantic.ts
View File

@@ -109,7 +109,7 @@ export function toFinishReasons(candidates?: Candidate[]): OTelFinishReason[] {
export function toOutputType(requested_mime?: string): string | undefined {
switch (requested_mime) {
// explictly support the known good values of responseMimeType
// explicitly support the known good values of responseMimeType
case 'text/plain':
return OTelOutputType.TEXT;
case 'application/json':

2
packages/core/src/test-utils/mock-tool.ts
View File

@@ -182,7 +182,7 @@ export class MockModifiableTool
extends BaseDeclarativeTool<Record<string, unknown>, ToolResult>
implements ModifiableDeclarativeTool<Record<string, unknown>>
{
// Should be overrided in test file. Functionality will be updated in follow
// Should be overridden in test file. Functionality will be updated in follow
// up PR which has MockModifiableTool expect MockTool
executeFn: (params: Record<string, unknown>) => ToolResult | undefined = () =>
undefined;

2
packages/core/src/utils/schemaValidator.ts
View File

@@ -30,7 +30,7 @@ addFormatsFunc(ajValidator);
*/
export class SchemaValidator {
/**
* Returns null if the data confroms to the schema described by schema (or if schema
* Returns null if the data conforms to the schema described by schema (or if schema
* is null). Otherwise, returns a string describing the error.
*/
static validate(schema: unknown | undefined, data: unknown): string | null {