Refactor technical indicators module and enhance structure
- Introduced a dedicated sub-package for technical indicators under `data/common/indicators/`, improving modularity and maintainability. - Moved `TechnicalIndicators` and `IndicatorResult` classes to their respective files, along with utility functions for configuration management. - Updated import paths throughout the codebase to reflect the new structure, ensuring compatibility. - Added comprehensive safety net tests for the indicators module to verify core functionality and prevent regressions during refactoring. - Enhanced documentation to provide clear usage examples and details on the new package structure. These changes improve the overall architecture of the technical indicators module, making it more scalable and easier to manage.
This commit is contained in:
@@ -17,7 +17,8 @@ from ..error_handling import (
|
||||
)
|
||||
|
||||
from .base import BaseLayer, LayerConfig
|
||||
from data.common.indicators import TechnicalIndicators, OHLCVCandle
|
||||
from data.common.indicators import TechnicalIndicators
|
||||
from data.common.data_types import OHLCVCandle
|
||||
from components.charts.utils import get_indicator_colors
|
||||
from utils.logger import get_logger
|
||||
|
||||
|
||||
@@ -14,7 +14,8 @@ from dataclasses import dataclass
|
||||
|
||||
from .base import BaseChartLayer, LayerConfig
|
||||
from .indicators import BaseIndicatorLayer, IndicatorLayerConfig
|
||||
from data.common.indicators import TechnicalIndicators, IndicatorResult, OHLCVCandle
|
||||
from data.common.indicators import TechnicalIndicators, IndicatorResult
|
||||
from data.common.data_types import OHLCVCandle
|
||||
from components.charts.utils import get_indicator_colors
|
||||
from utils.logger import get_logger
|
||||
from ..error_handling import (
|
||||
|
||||
Reference in New Issue
Block a user