16 Commits (21a353e9c25017a8a66661edb2ed98e9b152572b)

Author	SHA1	Message	Date
William FH	576880abc5	Re-use Trajectory Evaluator (#7248) ... Use the trajectory eval chain in the run evaluation implementation and update the prepare inputs method to apply to both asynca nd sync	1 year ago
Zander Chase	c460b04c64	Update String Evaluator (#6615) ... - Add protocol for `evaluate_strings` - Move the criteria evaluator out so it's not restricted to being applied on traced runs	1 year ago
Leonid Ganeline	c7ca350cd3	Fix class promotion (#6187) ... In LangChain, all module classes are enumerated in the `__init__.py` file of the correspondent module. But some classes were missed and were not included in the module `__init__.py` This PR: - added the missed classes to the module `__init__.py` files - `__init__.py:__all_` variable value (a list of the class names) was sorted - `langchain.tools.sql_database.tool.QueryCheckerTool` was renamed into the `QuerySQLCheckerTool` because it conflicted with `langchain.tools.spark_sql.tool.QueryCheckerTool` - changes to `pyproject.toml`: - added `pgvector` to `pyproject.toml:extended_testing` - added `pandas` to `pyproject.toml:[tool.poetry.group.test.dependencies]` - commented out the `streamlit` from `collbacks/__init__.py`, It is because now the `streamlit` requires Python >=3.7, !=3.9.7 - fixed duplicate names in `tools` - fixed correspondent ut-s #### Who can review? @hwchase17 @dev2049	1 year ago
Blithe	e31705b5ab	convert the parameter 'text' to uppercase in the function 'parse' of the class BooleanOutputParser (#5397) ... when the LLMs output 'yes|no'，BooleanOutputParser can parse it to 'True|False', fix the ValueError in parse(). <!-- when use the BooleanOutputParser in the chain_filter.py, the LLMs output 'yes|no'，the function 'parse' will throw ValueError。 --> Fixes # (issue) #5396 https://github.com/hwchase17/langchain/issues/5396 --------- Co-authored-by: gaofeng27692 <gaofeng27692@hundsun.com>	1 year ago
Harrison Chase	2da8c48be1	Harrison/datetime parser (#4693) ... Co-authored-by: Jacob Valdez <jacobfv@msn.com> Co-authored-by: Jacob Valdez <jacob.valdez@limboid.ai> Co-authored-by: Eugene Yurtsev <eyurtsev@gmail.com>	1 year ago
Harrison Chase	6df90ad9fd	handle json parsing errors (#5371) ... adds tests cases, consolidates a lot of PRs	1 year ago
Harrison Chase	179ddbe88b	add enum output parser (#5165)	1 year ago
Harrison Chase	94cf391ef1	standardize json parsing (#5168) ... Co-authored-by: Dev 2049 <dev.dev2049@gmail.com>	1 year ago
Harrison Chase	f5e2f70115	Harrison/json new line (#4646) ... Co-authored-by: David Chen <davidchen@gliacloud.com>	1 year ago
Sunish Sheth	812e5f43f5	Add _type for all parsers (#4189) ... Used for serialization. Also add test that recurses through our subclasses to check they have them implemented Would fix https://github.com/hwchase17/langchain/issues/3217 Blocking: https://github.com/mlflow/mlflow/pull/8297 --------- Signed-off-by: Sunish Sheth <sunishsheth2009@gmail.com> Co-authored-by: Dev 2049 <dev.dev2049@gmail.com>	1 year ago
Roma	d15f481352	Add unit test to output parsers (#3911) ... This pull request adds unit tests for various output parsers (BooleanOutputParser, CommaSeparatedListOutputParser, and StructuredOutputParser) to ensure their correct functionality and to increase code reliability and maintainability. The tests cover both valid and invalid input cases. Changes: Added unit tests for BooleanOutputParser. Added unit tests for CommaSeparatedListOutputParser. Added unit tests for StructuredOutputParser. Testing: All new unit tests have been executed, and they pass successfully. The overall test suite has been run, and all tests pass. Notes: These tests cover both successful parsing scenarios and error handling for invalid inputs. If any new output parsers are added in the future, corresponding unit tests should also be created to maintain coverage.	1 year ago
Eugene Yurtsev	055f58960a	Fix pytest collection warning (#3651) ... Fixes a pytest collection warning because the test class starts with the prefix "Test"	1 year ago
Nuno Campos	dac32c59e5	Nc/combining output parser (#3014) ... Co-authored-by: vowelparrot <130414180+vowelparrot@users.noreply.github.com>	1 year ago
Joshua Snyder	59d054308c	Add type inference for output parsers (#2769) ... Currently, the output type of a number of OutputParser's `parse` methods is `Any` when it can in fact be inferred. This PR makes BaseOutputParser use a generic type and fixes the output types of the following parsers: - `PydanticOutputParser` - `OutputFixingParser` - `RetryOutputParser` - `RetryWithErrorOutputParser` The output of the `StructuredOutputParser` is corrected from `BaseModel` to `Any` since there are no type guarantees provided by the parser. Fixes issue #2715	2 years ago
Daniel Chalef	6598beacdb	PydanticOutputParser unit test (#2047) ... Unit test for PydanticOutputParser --------- Co-authored-by: Daniel Chalef <daniel.chalef@private.org>	2 years ago
Luis	562d9891ea	Add regex dict: (#1616) ... This class enables us to send a dictionary containing an output key and the expected format, which in turn allows us to retrieve the result of the matching formats and extract specific information from it. To exclude irrelevant information from our return dictionary, we can prompt the LLM to use a specific command that notifies us when it doesn't know the answer. We refer to this variable as the "no_update_value". Regarding the updated regular expression pattern (r"{}:\s?([^.'\n']*).?"), it enables us to retrieve a format as 'Output Key':'value'. We have improved the regex by adding an optional space between ':' and 'value' with "s?", and by excluding points and line jumps from the matches using "[^.'\n']*".	2 years ago