rename config lazy object to current_config

Author: eadwinCode

docs/basics/application-context.md

@@ -1,22 +1,22 @@
-# **Application Context**
+# **Injector Context**
 
 In the complex web of dependencies within Ellar, 
 accessing the application instance without triggering circular import errors can be a daunting task. 
 
-To address this challenge, Ellar introduces the concept of an application context, 
+To address this challenge, Ellar introduces the concept of an injector context, 
 a powerful mechanism that facilitates smooth access to the application instance throughout various parts of the codebase.
 
-## **Understanding the Application Context**
+## **Understanding the Injector Context**
 
-The application context serves as a bridge between different components of the application, making the application object 
+The Injector context serves as a bridge between different components of the application, making the application object 
 readily available through the application Dependency Injection (DI) container. This ensures that you can access the 
 application instance without encountering import issues, whether it's during request handling, execution of CLI commands, 
 or manual invocation of the context.
 
 Two key elements of the application context are:
 
 - **current_injector**: This proxy variable refers to the current application **injector**, providing access to any service or the application instance itself.
-- **config**: A lazy loader for application configuration, which is based on the `ELLAR_CONFIG_MODULE` reference or accessed through `application.config` when the application context is active.
+- **current_config**: A lazy loader for application configuration, which is based on the `ELLAR_CONFIG_MODULE` reference or accessed through `application.config` when the application context is active.
 
 ## **Integration with Click Commands**
 
@@ -27,7 +27,7 @@ For instance, consider the following example:
 
 ```python
 import ellar_cli.click as click
-from ellar.app import current_injector
+from ellar.core import current_injector
 from ellar.di import injectable
 
 @injectable
@@ -37,7 +37,7 @@ class MyService:
 
 @click.command()
 @click.argument('name')
-@click.with_app_context
+@click.with_injector_context
 def my_command(name: str):
     my_service = current_injector.get(MyService)
     my_service.do_something()
@@ -63,8 +63,9 @@ For example, consider the following event handling setup:
 
 ```python
 from ellar.events import app_context_teardown, app_context_started
-from ellar.app import App, AppFactory, current_injector
-from ellar.threading import run_as_async
+from ellar.app import App, AppFactory
+from ellar.core import current_injector, injector_context
+from ellar.threading import run_as_sync
 
 @app_context_started.connect
 async def on_context_started():
@@ -76,9 +77,9 @@ def on_context_ended():
 
 app = AppFactory.create_app()
 
-@run_as_async
+@run_as_sync
 async def run_app_context():
-    async with app.application_context() as ctx:
+    async with injector_context(app.injector) as ctx:
         print("-----> Context is now available <------")
 
         app_instance = ctx.injector.get(App)

docs/cli/custom-commands.md

@@ -38,10 +38,10 @@ ARGUMENTS:
   --help     Show this message and exit.
 ```
 
-## **With App Context Decorator**
+## **With Injector Context Decorator**
 The `ellar_cli.click` module includes a command decorator function called `with_injector_context`. 
 This decorator ensures that a click command is executed within the application context, 
-allowing `current_injector`, and `config` to have values.
+allowing `current_injector`, and `current_config` to have values.
 
 For instance:
 

docs/overview/exception_handling.md

@@ -10,8 +10,8 @@ it is intercepted by this middleware, which then automatically sends an appropri
 }
 ```
 Depending on the application's configuration and the value of `DEBUG`, the exception handling behavior differs. 
-When `config.DEBUG` is True, the exception that is raised is shown to the client for easy error debugging. 
-However, when `config.DEBUG` is False, a 500 error is returned to the client, as illustrated below:
+When `current_config.DEBUG` is True, the exception that is raised is shown to the client for easy error debugging. 
+However, when `current_config.DEBUG` is False, a 500 error is returned to the client, as illustrated below:
 
 ```json
 {

tests/test_application/test_app_context.py

@@ -3,7 +3,7 @@
 import pytest
 from ellar.app import App
 from ellar.common import Body, post
-from ellar.core import Config, config, current_injector, injector_context
+from ellar.core import Config, current_config, current_injector, injector_context
 from ellar.testing import Test
 
 
@@ -25,12 +25,12 @@ async def test_current_config_fails_when_there_is_no_ellar_config_module(
 
         async with injector_context(tm.create_application().injector):
             assert current_injector.get(App) is not None
-            assert config.DEBUG is False
+            assert current_config.DEBUG is False
 
         assert caplog.text == ""
 
     with caplog.at_level(logging.WARNING):
-        assert config.DEBUG is False
+        assert current_config.DEBUG is False
         print(caplog.text)
         assert (
             "You are trying to access app config outside app "
@@ -64,7 +64,7 @@ async def test_current_config_works(anyio_backend):
 
     async with injector_context(tm.create_application().injector):
         app = current_injector.get(App)
-        assert app.config.FRAMEWORK_NAME == config.FRAMEWORK_NAME
+        assert app.config.FRAMEWORK_NAME == current_config.FRAMEWORK_NAME
 
     with pytest.raises(RuntimeError):
         current_injector.get(App)
@@ -76,7 +76,7 @@ def add(a: Body[int], b: Body[int]):
         from ellar.core import current_injector
 
         config_ = current_injector.get(Config)
-        assert config_.FRAMEWORK_NAME == config.FRAMEWORK_NAME
+        assert config_.FRAMEWORK_NAME == current_config.FRAMEWORK_NAME
         return a + b
 
     tm = Test.create_test_module(
@@ -87,7 +87,7 @@ def add(a: Body[int], b: Body[int]):
         res = tm.get_test_client().post("/", json={"a": 1, "b": 4})
         assert res.json() == 5
         config_ = current_injector.get(Config)
-        assert config_.FRAMEWORK_NAME == config.FRAMEWORK_NAME
+        assert config_.FRAMEWORK_NAME == current_config.FRAMEWORK_NAME
 
     with pytest.raises(RuntimeError):
         current_injector.get(Config)