auto_extended_mode no longer utilized, but settings and documentation remain

[buddhamangler-cbre]

trafficstars

Bug details

It appears auto_extended_mode setting is no longer utilized, yet configuration and documentation remain for the setting. What is the state of extended mode? I can't find any code that interacts with this setting anymore. It is not clear to me, it must be related to this decoupled commit, but it is not clear what this decoupling feature does. Does it make the extended mode obsolete?

https://github.com/qodo-ai/pr-agent/commit/d16012a5685d705e98f8158a66dabedd72048e89#diff-b57ba775e741d6f80bc4f8154b71330c011dae0ac43f3d0197e785b3e6b7117b

[qodo-merge-for-open-source[bot]]

:bulb: Auto-generated documentation-based answer:

The auto_extended_mode parameter has been renamed to auto_extended_mode in the PR-Agent/Qodo Merge codebase. This change was part of a refactoring effort to decouple the chunking mechanism from the extended mode.

Currently, the state of extended mode is:

1. The parameter is now called auto_extended_mode (default is true)
2. When enabled, it automatically chunks the PR code and runs the tool on each chunk
3. This chunking mechanism helps process large PRs by dividing them into manageable pieces

You can find these settings in the configuration options for the improve tool:

[pr_code_suggestions]
auto_extended_mode = true
num_code_suggestions_per_chunk = 3
max_number_of_calls = 3

The decoupling feature mentioned in the commit doesn't make extended mode obsolete - it just separates the chunking mechanism from the extended mode concept, making the codebase more modular and easier to maintain.

Relevant Sources:

• https://qodo-merge-docs.qodo.ai//tools/improve#configuration-options
• https://qodo-merge-docs.qodo.ai//usage-guide/additional_configurations#working-with-large-prs

[mrT23]

the opposite. Auto-extend is now the default, and only, mode