Move dict.update (shallow copy) to deep_update

[NolanTrem]

Important

Replaces shallow dictionary updates with deep_update for nested updates, enhancing configuration handling and adding tests for validation.

• Behavior:
  • Replaces shallow dict.update with deep_update for nested dictionary updates in config.py.
  • Adds deep_update function to base_utils.py for recursive dictionary merging.
• Config Handling:
  • Updates R2RConfig in config.py to use deep_update for merging configurations.
  • Ensures nested configurations are preserved and new values are added correctly.
• Testing:
  • Adds test_config.py to test configuration loading, merging, and serialization.
  • Tests ensure that configurations maintain expected types and required keys are present.

^{This description was created by for eb116bc. It will automatically update as commits are pushed.}

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to eb116bc in 1 minute and 53 seconds

More details

• Looked at 532 lines of code in 9 files
• Skipped 0 files when reviewing.
• Skipped posting 3 drafted comments based on config settings.

1. py/core/base/utils/__init__.py:20

• Draft comment:
  The deep_update function is imported multiple times across different files. Consider centralizing the import to avoid redundancy.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The deep_update function is imported multiple times across different files. It would be more efficient to import it once in a shared module and use it from there.

2. py/core/utils/__init__.py:15

• Draft comment:
  The deep_update function is imported multiple times across different files. Consider centralizing the import to avoid redundancy.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The deep_update function is imported multiple times across different files. It would be more efficient to import it once in a shared module and use it from there.

3. py/shared/utils/__init__.py:18

• Draft comment:
  The deep_update function is imported multiple times across different files. Consider centralizing the import to avoid redundancy.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The deep_update function is imported multiple times across different files. It would be more efficient to import it once in a shared module and use it from there.

Workflow ID: wflow_IxdX50RIHqWdtJae

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.