-
Notifications
You must be signed in to change notification settings - Fork 405
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: gather context #5988
feat: gather context #5988
Conversation
@@ -140,6 +160,7 @@ export class MetadataOrchestrator { | |||
requests.push(request); | |||
} | |||
|
|||
const response = this.gatherContext(sourceUri); |
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.
@CristiCanizales I was thinking that context gathering would occur after eligibility is determined and the class is eligible for generation.
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.
Yes! Right now it's just like a placeholder so we can play with the response when doing prompt engineering
* chore: eligibility criteria for class and method annotations * chore: update rest-related annotations * feat: latest jorje jar * chore: pin vsp version
…orcedx-vscode into cristi/gather-context
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.
@CristiCanizales just a couple of var/label changes around eligibility. Could you do the noted changes in your next PR?
What does this PR do?
What issues does this PR fix or reference?
@W-17260440@