-
Notifications
You must be signed in to change notification settings - Fork 4
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
fix: Use types instead of interfaces #274
Conversation
Co-authored-by: Deeksha Sinha <[email protected]>
@@ -10,12 +10,12 @@ import type { LlmChoice } from './llm-choice.js'; | |||
/** | |||
* Results of each module. | |||
*/ | |||
export interface ModuleResults { | |||
export type ModuleResults = { | |||
grounding?: GenericModuleResult; |
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.
[req] We removed the grounding types from input, but this is still here
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.
This would also need a compatibility note.
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.
- removed the grounding key
- added compatibility note
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.
Already approving this (have disabled auto-merge). Please have a look into grounding in output.
Context
Due to some eslint rules, we used interfaces for some of the orchestration types by accident.
In order to keep the consistent UX, we will keep the original generated client.
Definition of Done