Skip to content

feat: Rename "remote API definitions" to "remote schema" throughout - #620

Merged
razor-x merged 2 commits into
mainfrom
claude/cli-schema-naming-181jn8
Aug 12, 2026
Merged

feat: Rename "remote API definitions" to "remote schema" throughout#620
razor-x merged 2 commits into
mainfrom
claude/cli-schema-naming-181jn8

Conversation

@razor-x

@razor-x razor-x commented Aug 12, 2026

Copy link
Copy Markdown
Member

This PR standardizes terminology across the codebase by renaming all references to "remote API definitions" to "remote schema". This improves clarity and consistency in naming conventions.

Key Changes

  • Renamed interaction module: use-remote-api-defs.tsuse-remote-schema.ts with updated function names and prompts
  • Updated config interface: Renamed getUseRemoteApiDefs/setUseRemoteApiDefs to getUseRemoteSchema/setUseRemoteSchema in CliConfig
  • Added backward compatibility: The config getter now checks both the new use_remote_schema key and the legacy use_remote_api_defs key, while the setter cleans up the old key
  • Renamed CLI command: config-use-remote-api-defs.tsconfig-use-remote-schema.ts with updated command path and descriptions
  • Updated CLI flags: --remote-api-defs--remote-schema in global flags
  • Updated API blueprint options: Renamed useRemoteDefinitions parameter to useRemoteSchema in getApiBlueprint()
  • Updated all documentation and comments: Changed references from "API definitions" to "API schema" throughout the codebase, including README, error messages, and inline comments

Implementation Details

  • The config migration is transparent: existing configurations using the old use_remote_api_defs key will continue to work, and new settings are stored under the new use_remote_schema key
  • All user-facing messages, command paths, and flag names have been updated to use the new terminology
  • The change maintains full backward compatibility while encouraging migration to the new naming convention

https://claude.ai/code/session_017bpiHstA7SLhudByn1Mog7

Rename the use-remote-api-defs idea to use-remote-schema throughout:

- `seam config use-remote-api-defs` -> `seam config use-remote-schema`
- `--remote-api-defs` -> `--remote-schema`
- config key `use_remote_api_defs` -> `use_remote_schema`, read with a
  fallback to the legacy key so existing configs keep their setting
- `getUseRemoteApiDefs`/`setUseRemoteApiDefs` -> `getUseRemoteSchema`/
  `setUseRemoteSchema`, `interactForUseRemoteApiDefs` ->
  `interactForUseRemoteSchema`, `useRemoteDefinitions` -> `useRemoteSchema`

Also say "Seam API schema" instead of "Seam API definitions" in the help
text, prompts, download messages, completion headers, and README.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017bpiHstA7SLhudByn1Mog7
@razor-x razor-x changed the title Rename "remote API definitions" to "remote schema" throughout feat: Rename "remote API definitions" to "remote schema" throughout Aug 12, 2026
@razor-x
razor-x marked this pull request as ready for review August 12, 2026 05:04
@razor-x
razor-x merged commit a7af22f into main Aug 12, 2026
14 checks passed
@razor-x
razor-x deleted the claude/cli-schema-naming-181jn8 branch August 12, 2026 05:10
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