Skip to content

Add TypeScript naming convention tip and update LangChain label#71

Merged
amavashev merged 2 commits intomainfrom
claude/fix-docs-naming-conventions-eed4F
Mar 16, 2026
Merged

Add TypeScript naming convention tip and update LangChain label#71
amavashev merged 2 commits intomainfrom
claude/fix-docs-naming-conventions-eed4F

Conversation

@amavashev
Copy link
Contributor

Summary

This PR makes two documentation improvements: adding a helpful tip about TypeScript naming conventions for the CyclesClient, and updating the navigation label for the LangChain Python integration guide.

Key Changes

  • Added a tip box in the "Using the Cycles Client Programmatically" guide explaining that CyclesClient methods use snake_case JSON format, with a reference to typed mapper functions for camelCase convenience in TypeScript
  • Updated the sidebar navigation label from "LangChain (Python)" to "LangChain.py" for consistency with the "LangChain.js" naming convention

Details

The new tip directs TypeScript users to the appropriate mapper functions (reservationCreateRequestToWire, reservationCreateResponseFromWire, etc.) documented in the TypeScript Getting Started guide, improving the developer experience when working with the programmatic client.

https://claude.ai/code/session_016DVLLHvBEwzfixanGnKVQR

claude and others added 2 commits March 16, 2026 20:39
…nt guide

The programmatic client page shows TypeScript examples using wire-format
(snake_case) JSON without explaining why, which could confuse developers
expecting camelCase. Add a tip callout matching the note already present
in the TypeScript getting-started guide.

https://claude.ai/code/session_016DVLLHvBEwzfixanGnKVQR
update post title
@amavashev amavashev merged commit 435677e into main Mar 16, 2026
1 check passed
@amavashev amavashev deleted the claude/fix-docs-naming-conventions-eed4F branch March 22, 2026 08:43
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