Release v0.1.19

#### Added
- Unified import interface: all core classes and functions can now be imported directly from `api_exception` (e.g. `from api_exception import ResponseModel, APIException`).
- Cleaner `__init__.py` exports with `__all__`.

#### Changed
- Internal imports refactored, simplified folder structure for `enums.py`, `response_model.py`, `rfc7807_model.py`.

#### Fixed
- Example and README imports updated to use new unified style.

Author: akutayural

README.md

@@ -410,9 +410,22 @@ Benchmark scripts and raw Locust reports are available in the [benchmark](https:
 
 ## 📜 Changelog
 
-**v0.1.18 - 2025-08-17**
+**v0.1.19 - 2025-08-18**
+✅ **Initial stable and suggested version**
+
+
+#### Added
+- Unified import interface: all core classes and functions can now be imported directly from `api_exception` (e.g. `from api_exception import ResponseModel, APIException`).
+- Cleaner `__init__.py` exports with `__all__`.
+
+#### Changed
+- Internal imports refactored, simplified folder structure for `enums.py`, `response_model.py`, `rfc7807_model.py`.
+
+#### Fixed
+- Example and README imports updated to use new unified style.
 
-✅ **Initial stable version**
+
+**v0.1.18 - 2025-08-17**
 
 #### Added
 - Global logging control (`set_global_log`) with `log` param in `register_exception_handlers`.

api_exception/__init__.py

@@ -5,11 +5,11 @@
 from fastapi.responses import JSONResponse
 from starlette.status import HTTP_422_UNPROCESSABLE_ENTITY
 
-from schemas.rfc7807_model import RFC7807ResponseModel
+from api_exception.rfc7807_model import RFC7807ResponseModel
 from .logger import logger, add_file_handler
 from .exception import APIException, set_default_http_codes, DEFAULT_HTTP_CODES, set_global_log
-from custom_enum.enums import ExceptionCode, ExceptionStatus, BaseExceptionCode, ResponseFormat
-from schemas.response_model import ResponseModel
+from api_exception.enums import ExceptionCode, ExceptionStatus, BaseExceptionCode, ResponseFormat
+from api_exception.response_model import ResponseModel
 from .response_utils import APIResponse
 import traceback
 

custom_enum/enums.py renamed to api_exception/enums.py

@@ -2,10 +2,10 @@
 import traceback
 from typing import Union
 
-from schemas.rfc7807_model import RFC7807ResponseModel
+from api_exception.rfc7807_model import RFC7807ResponseModel
 from .logger import logger
-from custom_enum.enums import ExceptionCode, ExceptionStatus
-from schemas.response_model import ResponseModel
+from api_exception.enums import ExceptionCode, ExceptionStatus
+from api_exception.response_model import ResponseModel
 
 GLOBAL_LOG: bool = True
 

api_exception/exception.py

@@ -1,6 +1,6 @@
 from typing import Generic, TypeVar, Optional
-from pydantic import BaseModel, Field, ConfigDict
-from custom_enum.enums import ExceptionStatus
+from pydantic import BaseModel, Field
+from api_exception.enums import ExceptionStatus
 
 # Generic type for response data
 DataT = TypeVar('DataT')

schemas/response_model.py renamed to api_exception/response_model.py

@@ -1,7 +1,7 @@
 from typing import Dict
-from schemas.response_model import ResponseModel
-from custom_enum.enums import ExceptionStatus, BaseExceptionCode
-from schemas.rfc7807_model import RFC7807ResponseModel
+from api_exception.response_model import ResponseModel
+from api_exception.enums import ExceptionStatus, BaseExceptionCode
+from api_exception.rfc7807_model import RFC7807ResponseModel
 
 
 class APIResponse:

api_exception/response_utils.py

@@ -40,13 +40,13 @@ You get two powerful behaviors:
 If you want to log your own events (not just exceptions), you can use the built-in logger:
 
 ```python
-from api_exception.logger import logger
+from api_exception import logger
 logger.warning("This will be logged to both console and file")
 logger.info("This INFO log will also be written to the file"
 ```
 Also you can call add_file_handler to write log to file
 ```python
-from api_exception.logger import add_file_handler,logger
+from api_exception import add_file_handler,logger
 add_file_handler("api_exception.log", level=logging.DEBUG)
 logger.warning("This will be logged to both console and file")
 ```

schemas/rfc7807_model.py renamed to api_exception/rfc7807_model.py

@@ -23,8 +23,7 @@ RFC 7807 ensures every failure tells the same story — clearly, consistently, a
 To enable RFC 7807 response formatting across your application:
 
 ```python
-from api_exception import register_exception_handlers
-from api_exception.enums import ResponseFormat
+from api_exception import register_exception_handlers, ResponseFormat
 from fastapi import FastAPI
 
 app = FastAPI()
@@ -39,8 +38,8 @@ This will return error responses with the application/problem+json content type,
 ### 🧪 RFC7807 Usage Example
 ```python
 from api_exception import APIException, APIResponse
-from api_exception.enums import ResponseFormat
-from api_exception.models import ResponseModel
+from api_exception import ResponseFormat
+from api_exception import ResponseModel
 from fastapi import FastAPI
 from .schemas import UserResponse
 from .exceptions import CustomExceptionCode

docs/advanced/logging.md

@@ -60,8 +60,8 @@ In **Swagger UI**, your custom error cases will show up clearly alongside your s
 The exception messages will be formatted as RFC 7807.
 
 ```python
-from schemas.response_model import ResponseModel
-from api_exception import APIResponse
+from api_exception import ResponseModel, APIResponse
+
 
 @app.get(
     "/rfc7807",