Enforce your style guide: format inline code in LangChain example - #333
Open
mintlify[bot] wants to merge 4 commits into
Open
Enforce your style guide: format inline code in LangChain example#333mintlify[bot] wants to merge 4 commits into
mintlify[bot] wants to merge 4 commits into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Style-consistency passes on pages touched by recent PRs: the LangChain/LangSmith example (from #332's scope) and the checkpointing failure sections (from #335).
Changes
v4/examples/langchain-langsmith.mdx: setbind_tools,book_slot,eventTypeId,chat_history,RunnableWithMessageHistory(), andpredictin code formatting to match how other identifiers are formatted on the pageperformance/checkpointing.mdx: replaced em-dash clause joiners with separate sentences, used a colon before the allocation examples, split a 40-word support-email sentence, changed "app id" to "app ID", aligned "before vLLM is imported" with the page's "before importing vLLM" phrasing, and converted an HTML comment to MDX comment syntax (the HTML comment failed MDX parsing)partner-services/deepgram.mdx: reviewed, already consistent; no changesContext
Triggered by the merges of #332 and #335. Headings and their anchors were left untouched; the checkpoint agent deep-links to them. No technical content or code samples changed.