-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
feat:Add new API endpoint for last applied rule and update RuleLogSchema #115
Conversation
WalkthroughThe changes involve modifications to the Changes
Possibly related PRs
Suggested reviewers
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (2)
src/libs/LangSmith/openapi.yaml (2)
3881-3882
: Enhance endpoint documentation
The current description "Get the last applied rule" is too brief. Consider expanding it to include:
- The purpose and use case of this endpoint
- What "last applied" means in this context
- Any important behavior details or side effects
16605-16609
: Add documentation for the application_time field
While the field is properly typed, consider adding a description to clarify:
- The exact meaning of "application time"
- When this timestamp is set
- Why it might be null
Example addition:
application_time:
title: Application Time
+ description: Timestamp when the rule was last applied to a run. Null if the rule hasn't been applied yet.
type: string
format: date-time
nullable: true
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
⛔ Files ignored due to path filters (6)
src/libs/LangSmith/Generated/LangSmith.DatasetsClient.UpdateDataset.g.cs
is excluded by!**/generated/**
src/libs/LangSmith/Generated/LangSmith.IDatasetsClient.UpdateDataset.g.cs
is excluded by!**/generated/**
src/libs/LangSmith/Generated/LangSmith.IRunClient.GetLastAppliedRule.g.cs
is excluded by!**/generated/**
src/libs/LangSmith/Generated/LangSmith.Models.DatasetUpdate.g.cs
is excluded by!**/generated/**
src/libs/LangSmith/Generated/LangSmith.Models.RuleLogSchema.g.cs
is excluded by!**/generated/**
src/libs/LangSmith/Generated/LangSmith.RunClient.GetLastAppliedRule.g.cs
is excluded by!**/generated/**
📒 Files selected for processing (1)
- src/libs/LangSmith/openapi.yaml (3 hunks)
🔇 Additional comments (2)
src/libs/LangSmith/openapi.yaml (2)
13010-13015
: LGTM: Valid schema extension
The inputs_filters field is properly defined with clear typing and nullability.
3877-3908
: LGTM: Well-structured endpoint definition
The endpoint is well-designed with:
- Proper REST conventions
- Comprehensive security controls
- Appropriate parameter validation
- Clear error responses
Let's verify the referenced schema exists:
✅ Verification successful
Schema verification complete - endpoint is correctly defined
The RuleLogSchema referenced in the endpoint is properly defined with all required fields (rule_id, run_id, start_time, end_time) and appropriate data types, including UUID formats for IDs and date-time formats for timestamps. The schema definition aligns perfectly with the endpoint's purpose of retrieving the last applied rule.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Verify that RuleLogSchema is properly defined
rg -A 10 "RuleLogSchema:" src/libs/LangSmith/openapi.yaml
Length of output: 273
Script:
#!/bin/bash
# Let's get the complete RuleLogSchema definition to verify all required properties
rg -A 20 "RuleLogSchema:" src/libs/LangSmith/openapi.yaml
Length of output: 497
Script:
#!/bin/bash
# Let's get even more lines to see the complete schema definition including start_time and end_time
rg -A 30 "RuleLogSchema:" src/libs/LangSmith/openapi.yaml
Length of output: 736
Script:
#!/bin/bash
# One final check with even more lines to see the complete schema including end_time
rg -A 40 "RuleLogSchema:" src/libs/LangSmith/openapi.yaml
Length of output: 993
Summary by CodeRabbit