Tr/dynamic context

[mrT23]

PR Type

Enhancement, Documentation

---

Description

• Implemented dynamic context as the default strategy for PR-Agent
• Added comprehensive documentation explaining the dynamic context approach, its benefits, and challenges
• Updated configuration settings to enable dynamic context by default
• Adjusted context extension parameters in documentation and configuration files
• Announced the new default dynamic context option in the README

---

Changes walkthrough 📝

	Relevant files
Documentation	README.md Update README with dynamic context announcement                    README.md Added news update about dynamic context becoming the default option Briefly explained the benefits of dynamic context for PR-Agent +4/-0      dynamic_context.md Add detailed documentation for dynamic context strategy    docs/docs/core-abilities/dynamic_context.md Added comprehensive documentation on dynamic context strategy Explained challenges of expanding context window Described asymmetric and dynamic context approach Included configuration options for dynamic context +67/-2    additional_configurations.md Update context extension configuration documentation          docs/docs/usage-guide/additional_configurations.md Updated context extension parameters Removed specific tool mentions for context extension +3/-3
Configuration changes	configuration.toml Update configuration to enable dynamic context                      pr_agent/settings/configuration.toml Enabled dynamic context by default Adjusted max_extra_lines_before_dynamic_context from 10 to 8 +2/-2

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[qodo-merge-pro]

PR Reviewer Guide 🔍

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🏅 Score: 95

🧪 No relevant tests

🔒 No security concerns identified

🔀 Multiple PR themes Sub-PR theme: Update README with dynamic context announcement Relevant files: README.md Sub-PR theme: Add and update documentation for dynamic context Relevant files: docs/docs/core-abilities/dynamic_context.md docs/docs/usage-guide/additional_configurations.md Sub-PR theme: Enable dynamic context by default in configuration Relevant files: pr_agent/settings/configuration.toml

⚡ No key issues to review

[qodo-merge-pro]

PR Code Suggestions ✨

Category	Suggestion	Score
Enhancement	Add an example to illustrate the asymmetric context strategy Consider adding a brief example or use case to illustrate how the asymmetric and dynamic context strategy works in practice. This will help readers better understand the concept. docs/docs/core-abilities/dynamic_context.md [43-49] **Asymmetric:** We start by recognizing that the context preceding a code change is typically more crucial for understanding the modification than the context following it. Consequently, PR-Agent implements an asymmetric context policy, decoupling the context window into two distinct segments: one for the code before the change and another for the code after. -By independently adjusting each context window, PR-Agent can supply the model with a more tailored and pertinent context for individual code changes. +By independently adjusting each context window, PR-Agent can supply the model with a more tailored and pertinent context for individual code changes. +For example, when analyzing a change within a function, PR-Agent might provide more context lines before the change to include the function signature and any relevant variable declarations, while limiting the context after the change to focus on the immediate impact of the modification. + Apply this suggestion Suggestion importance[1-10]: 9 Why: Adding a practical example significantly improves the understanding of the asymmetric context strategy, making the concept more concrete for readers.	9
	Add explanation of how dynamic context improves code understanding Consider adding a brief explanation of how the dynamic context strategy improves the model's understanding of code changes. This will help readers better grasp the benefits of this approach. docs/docs/core-abilities/dynamic_context.md [52-55] **Dynamic:** -We also employs a "dynamic" context strategy. +We also employ a "dynamic" context strategy. We recognize that the optimal context for a code change often corresponds to its enclosing code component (e.g., function, class), rather than a fixed number of lines. Consequently, we dynamically adjust the context window based on the code's structure, ensuring the model receives the most pertinent information for each modification. +This approach significantly enhances the model's ability to understand the purpose and impact of code changes within their functional context, leading to more accurate and insightful analyses. Apply this suggestion Suggestion importance[1-10]: 8 Why: The suggestion adds valuable information about the benefits of dynamic context, which enhances the documentation's clarity and usefulness.	8
	Add guidance on customizing dynamic context behavior Consider adding a brief explanation of how users can customize or fine-tune the dynamic context behavior if needed. This information would be valuable for advanced users who might want to adjust the strategy for their specific use cases. docs/docs/core-abilities/dynamic_context.md [59-67] ## Appendix - relevant configuration options [config] patch_extension_skip_types =[".md",".txt"] # Skip files with these extensions when trying to extend the context allow_dynamic_context=true # Allow dynamic context extension max_extra_lines_before_dynamic_context = 8 # will try to include up to X extra lines before the hunk in the patch, until we reach an enclosing function or class patch_extra_lines_before = 3 # Number of extra lines (+3 default ones) to include before each hunk in the patch patch_extra_lines_after = 1 # Number of extra lines (+3 default ones) to include after each hunk in the patch +Users can adjust these configuration options to fine-tune the dynamic context behavior. For instance, increasing `max_extra_lines_before_dynamic_context` will allow for more context to be included, which might be beneficial for complex codebases. However, be cautious as setting this value too high might lead to performance issues or overwhelm the model with unnecessary information. + Apply this suggestion Suggestion importance[1-10]: 7 Why: This suggestion provides useful information for advanced users, enhancing the documentation's completeness, but it's not as critical as the previous two suggestions.	7

[mrT23]

/analyze

[qodo-merge-pro]

The analyze command only supports the following languages: python, java, cpp, javascript, typescript, jsx, tsx, csharp