-
Notifications
You must be signed in to change notification settings - Fork 3
Dev #7
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
Dev #7
Conversation
- chunk attribution - chunk utilization - eval ranking - JSON Schema Validation
…suring compatibility with the latest fi-instrumentation-otel version.
Add new evaluation
|
Caution Review failedThe pull request is closed. WalkthroughThis update introduces four new evaluation types to the core instrumentation types and expands their configuration and mapping logic. Across all framework integrations, documentation examples for registering trace providers are simplified by removing version and session parameters. All related framework packages and dependencies are updated to version 0.1.4 for consistency. Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant Framework
participant TraceProvider
User->>Framework: import and call register(project_type, project_name)
Framework->>TraceProvider: register(project_type, project_name)
TraceProvider-->>Framework: Trace provider initialized
Framework-->>User: Ready to trace
sequenceDiagram
participant EvalCaller
participant EvalConfig
participant EvalMappingConfig
EvalCaller->>EvalConfig: get_config_for_eval(eval_name)
EvalConfig-->>EvalCaller: Return config dict (supports new eval types)
EvalCaller->>EvalMappingConfig: get_mapping_for_eval(eval_name)
EvalMappingConfig-->>EvalCaller: Return mapping dict (supports new eval types)
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (36)
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. 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 (
|
Pull Request
Description
Describe the changes in this pull request:
Checklist
Related Issues
Closes #<issue_number>
Summary by CodeRabbit
New Features
Documentation
Chores