CD-7372 API for Code Snippet Context Extraction Based on Rule Complexity#630
Open
neha-naazneen wants to merge 4 commits into
Open
CD-7372 API for Code Snippet Context Extraction Based on Rule Complexity#630neha-naazneen wants to merge 4 commits into
neha-naazneen wants to merge 4 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Design a new AI Code Context API that consolidates relevant violation metadata and dynamically extracts code snippets based on the rule complexity level (Low, Medium, High) so that the AI model receives appropriate contextual information for accurate rule violation analysis and automated fix generation.
Hypothesis:
If we design an API that dynamically determines and returns structured code context data (line, method, or class) based on rule severity, then the AI model will have optimal and consistent contextual information for each violation. This will improve accuracy in auto-fixes, reduce false positives, and enable scalable integration across rule sets.
The API should return a JSON response containing: