Configuration

The package works with zero configuration; publishing the config file only lets you change the defaults in one place. The published config/trading-analytics.php:

return [
    // Default decimal precision (bcmath scale) for every calculation.
    'scale' => env('TRADING_ANALYTICS_SCALE', 10),

    // Default win-rate bucketing period: daily, weekly, or monthly.
    'win_rate_period' => env('TRADING_ANALYTICS_WIN_RATE_PERIOD', 'daily'),
];

Every key

Environment

Both keys are env-driven, so you rarely need to publish the file at all:

TRADING_ANALYTICS_SCALE=4
TRADING_ANALYTICS_WIN_RATE_PERIOD=weekly

Per-run overrides

A run’s explicit ->scale(...) / ->usingWinRatePeriod(...) always overrides the configured default:

use RoundlyConsulting\TradingAnalytics\Enums\Period;
use RoundlyConsulting\TradingAnalytics\Facades\TradingAnalytics;

// A run's own settings always win over the configured defaults
$analytics = TradingAnalytics::for($trades)
    ->scale(2)
    ->usingWinRatePeriod(Period::WEEKLY)
    ->calculate();

$analytics->getScale(); // 2

The configured defaults are read when the engine is built, so a malformed scale or win_rate_period throws InvalidConfigurationException even for a run that then sets its own ->scale() or ->usingWinRatePeriod().

Outside a booted Laravel app (no config bound), the built-in defaults — scale 10 and daily — apply automatically, so the engine also runs in plain scripts and unit tests.