github/langchain
1
0
Fork 0
mirror of https://github.com/hwchase17/langchain.git synced 2025-06-25 16:13:25 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix typo in Custom Output Parser doc (#28617)

Browse Source 
- [x] Fix typo in Custom Output Parser doc
This commit is contained in:
Huy Nguyen 2024-12-10 02:14:00 +07:00 committed by GitHub
parent b476fdb54a
commit bdb4cf7cc0
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/docs/how_to/output_parser_custom.ipynb
View File

@ -12,7 +12,7 @@
"There are two ways to implement a custom parser:\n", "There are two ways to implement a custom parser:\n",
"\n", "\n",
"1. Using `RunnableLambda` or `RunnableGenerator` in [LCEL](/docs/concepts/lcel/) -- we strongly recommend this for most use cases\n", "1. Using `RunnableLambda` or `RunnableGenerator` in [LCEL](/docs/concepts/lcel/) -- we strongly recommend this for most use cases\n",
"2. By inherting from one of the base classes for out parsing -- this is the hard way of doing things\n", "2. By inheriting from one of the base classes for out parsing -- this is the hard way of doing things\n",
"\n", "\n",
"The difference between the two approaches are mostly superficial and are mainly in terms of which callbacks are triggered (e.g., `on_chain_start` vs. `on_parser_start`), and how a runnable lambda vs. a parser might be visualized in a tracing platform like LangSmith." "The difference between the two approaches are mostly superficial and are mainly in terms of which callbacks are triggered (e.g., `on_chain_start` vs. `on_parser_start`), and how a runnable lambda vs. a parser might be visualized in a tracing platform like LangSmith."
] ]
@ -200,7 +200,7 @@
"id": "24067447-8a5a-4d6b-86a3-4b9cc4b4369b", "id": "24067447-8a5a-4d6b-86a3-4b9cc4b4369b",
"metadata": {}, "metadata": {},
"source": [ "source": [
"## Inherting from Parsing Base Classes" "## Inheriting from Parsing Base Classes"
] ]
}, },
{ {
@ -208,7 +208,7 @@
"id": "9713f547-b2e4-48eb-807f-a0f6f6d0e7e0", "id": "9713f547-b2e4-48eb-807f-a0f6f6d0e7e0",
"metadata": {}, "metadata": {},
"source": [ "source": [
"Another approach to implement a parser is by inherting from `BaseOutputParser`, `BaseGenerationOutputParser` or another one of the base parsers depending on what you need to do.\n", "Another approach to implement a parser is by inheriting from `BaseOutputParser`, `BaseGenerationOutputParser` or another one of the base parsers depending on what you need to do.\n",
"\n", "\n",
"In general, we **do not** recommend this approach for most use cases as it results in more code to write without significant benefits.\n", "In general, we **do not** recommend this approach for most use cases as it results in more code to write without significant benefits.\n",
"\n", "\n",