-
Notifications
You must be signed in to change notification settings - Fork 133
add custom prompt option to text2cypher, tested #84
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
Conversation
Hey @a-s-g93, thanks for the contribution! To pass the CLA check you will need to sign our CLA, please follow the instructions here. |
Hey @willtai I sent an email yesterday with all required info before submitting my PR. How long before CLA info is verified? |
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.
Nice work! I would also add another test that raises SearchValidationError
when a wrong type is used for the custom prompt.
Something similar to this https://github.com/neo4j/neo4j-genai-python/blob/main/tests/unit/retrievers/test_text2cypher.py#L73
Thanks for the feedback @willtai! Should I test the |
Yes |
The PR E2E tests have been scaled down to avoid running out of disk space. Please rebase off the latest changes in main to apply these changes to your PR |
2d717a1
to
3773bc6
Compare
Co-authored-by: Alex Thomas <[email protected]>
Co-authored-by: Alex Thomas <[email protected]>
Co-authored-by: Alex Thomas <[email protected]>
Co-authored-by: Alex Thomas <[email protected]>
Co-authored-by: Alex Thomas <[email protected]>
765dfaf
to
3cd4644
Compare
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.
LGTM
Description
Add an option to provide a custom prompt to the Text2Cypher Retriever. Doing so will ignore any provided graph schema or examples.
Type of Change
Complexity
Low
Complexity:
How Has This Been Tested?
Checklist
The following requirements should have been met (depending on the changes in the branch):
no E2E tests needed, no examples written, no new files created