[BUG] refactor usage of extract() function to explicit variable assignments

[sancheet230]

Describe the bug.

The current implementation utilizes the extract() function to import variables from configuration arrays into the local scope. This practice can inadvertently overwrite existing variables or introduce unexpected behavior, especially if the configuration array contains unanticipated keys. To enhance code clarity and maintainability, it's advisable to replace extract() with explicit variable assignments

Expected behavior

The application should handle configuration data safely and predictably. Variables should be assigned explicitly from configuration arrays to prevent unintended overwrites and ensure clarity in the codebase. This approach enhances maintainability and reduces the risk of introducing hard-to-trace bugs

Screenshots

NA

How to Reproduce

1. Locate any method within the codebase that utilizes the extract() function to import variables from a configuration array.​

2. Ensure that the configuration array ($config) contains keys that match existing variable names in the local scope of the method.​

3. Execute the method and observe the behavior of the application.

🖥️ Device Information [optional]

• Operating System (OS):
• Browser:
• Browser Version:

👀 Have you checked for similar open issues?

• I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to work on this issue ?

Yes I am willing to submit a PR!

[github-actions]

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[sancheet230]

Currently working on this will raise a PR shortly

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️