Skip to content

Expose episode source argument when adding data #247

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

Merged
merged 45 commits into from
Apr 10, 2025
Merged

Expose episode source argument when adding data #247

merged 45 commits into from
Apr 10, 2025

Conversation

paul-paliychuk
Copy link
Contributor

@paul-paliychuk paul-paliychuk commented Apr 10, 2025

Important

Expose source_description argument in add() method of GraphClient and AsyncGraphClient, updating Episode model and bumping version to 2.10.1.

  • Behavior:
    • Expose source_description argument in add() method of GraphClient and AsyncGraphClient in client.py.
    • Update JSON payload in add() to include source_description.
  • Models:
    • Update Episode model in episode.py to include source_description as an optional field.
  • Versioning:
    • Bump version from 2.10.0 to 2.10.1 in pyproject.toml and client_wrapper.py.

This description was created by Ellipsis for 145126c. It will automatically update as commits are pushed.

Copy link
Contributor

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❌ Changes requested. Reviewed everything up to 145126c in 2 minutes and 26 seconds

More details
  • Looked at 192 lines of code in 5 files
  • Skipped 0 files when reviewing.
  • Skipped posting 5 drafted comments based on config settings.
1. src/zep_cloud/core/client_wrapper.py:17
  • Draft comment:
    SDK version updated to 2.10.1. Ensure all clients and documentation are in sync with this version change.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
    This comment is asking the PR author to ensure that all clients and documentation are in sync with the version change, which violates the rule against asking the author to ensure things are tested or verified. It also relates to a dependency change, which should not be commented on.
2. src/zep_cloud/graph/client.py:140
  • Draft comment:
    New 'add' method exposes 'source_description' and uses mandatory 'data' and 'type'. Verify these changes are covered in unit tests and that the documentation reflects the new parameters.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
    The comment asks the PR author to verify that changes are covered in unit tests and that documentation reflects new parameters. This violates the rule against asking the author to ensure changes are tested or documented.
3. src/zep_cloud/types/episode.py:15
  • Draft comment:
    Ensure that the new field 'source_description' is documented in your API docs and its intended usage is clearly explained.
  • Reason this comment was not posted:
    Comment was on unchanged code.
4. src/zep_cloud/graph/client.py:149
  • Draft comment:
    Improve docstring clarity by adding punctuation; for example, insert a semicolon after 'graph' in the note to separate ideas.
  • Reason this comment was not posted:
    Comment was not on a location in the diff, so it can't be submitted as a review comment.
5. src/zep_cloud/types/episode.py:11
  • Draft comment:
    The Episode model now correctly exposes 'source_description'; documentation and field aliasing appear consistent with the new API.
  • Reason this comment was not posted:
    Confidence changes required: 0% <= threshold 50%
    None

Workflow ID: wflow_zGMBruxmIWwBHmy9


Want Ellipsis to fix these issues? Tag @ellipsis-dev in a comment. You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

@paul-paliychuk paul-paliychuk merged commit 6c23f6c into main Apr 10, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant