-
Notifications
You must be signed in to change notification settings - Fork 15.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor: Improve logic for parsing google-Style docstrings #28730
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could you add some unit tests on cases that currently fail?
Hi @ccurme,Thank you for the feedback! I’m not very familiar with writing unit tests for this type of case. Could you please guide me. |
you can add some tests to and I'm curious what this aims to fix. If you can do it before the holidays let me know! Otherwise we can close this one and reopen with tests whenever you have time to do so! |
…atting and docstring
…e_docstring function
@efriis I’ve added tests to validate the updated _parse_google_docstring function, but some checks are failing. Could you help identify what’s going wrong? |
fixed the lint errors but the tests you added are failing. You can run them locally with
and for future reference you can run format/lint (what i fixed) with:
|
Thanks for the help! I now have a better understanding of how to do it. |
Thank you for contributing to LangChain!
Description:
Improved the
_parse_google_docstring
function inlangchain/core
to support parsing multi-paragraph descriptions before theArgs:
section while maintaining compliance with Google-style docstring guidelines. This change ensures better handling of docstrings with detailed function descriptions.Issue:
Fixes #28628
Dependencies:
None.
Twitter handle:
@isatyamks