Streamline Configuration Loading in Conversation Config Module

[Mefisto04]

This PR introduces several minor yet impactful changes to improve the robustness and clarity of the Conversation Configuration Module:

1. Improved Error Handling:

   • Catches specific exceptions like FileNotFoundError and yaml.YAMLError for clearer error messages.
   • Replaced print statements with logging for better output control.

2. Streamlined Configuration Loading:

   • Refactored the get_conversation_config_path method to reduce redundancy by using a loop to check for the configuration file in multiple locations.

3. Simplified Deep Copy Logic:

   • Enhanced clarity in the __init__ method by directly updating self.config_conversation with the loaded configuration, eliminating the need for deep copying.

These changes enhance the overall maintainability and error reporting of the module, providing a clearer understanding of issues during configuration loading.

Code Snippet

# Error Handling
except FileNotFoundError as e:
    logging.error(f"Error locating {config_file}: {str(e)}")
    return None
except yaml.YAMLError as e:
    logging.error(f"YAML Error: {str(e)}")
    return None

# Configuration Loading
for path in [base_path, os.path.dirname(base_path), os.getcwd()]:
    config_path = os.path.join(path, config_file)
    if os.path.exists(config_path):
        return config_path

# Deep Copy Logic
self.config_conversation.update(config_conversation)

[Mefisto04]

hey @souzatharsis please review this

[souzatharsis]

Will do, apologies I was out this week.

…

On Thu, Oct 24, 2024 at 4:56 PM Mayur Kawale ***@***.***> wrote: hey @souzatharsis <https://github.com/souzatharsis> please review this — Reply to this email directly, view it on GitHub <#95 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADTMY3LJM72UHAQ4ACU55SDZ5FGHFAVCNFSM6AAAAABQK5GMFGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZWGIZDQMRVHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[souzatharsis]

automated tests indicate api keys are not found. please check above logs.