Weave Code
Trading Analytics For Laravel Laravel Package
roundly-consulting/trading-analytics-for-laravel
Trading Analytics for Laravel brings trading performance analysis into your Laravel apps, offering metrics, reporting, and integration-friendly APIs for building dashboards and market insights.
Calculate trading performance analytics — P&L, returns, streaks, profit factor — for Laravel.
Frequently asked questions about Trading Analytics For Laravel
- What Laravel and PHP versions does roundly-consulting/trading-analytics-for-laravel support?
- The release notes provided do not state supported Laravel and PHP versions, so confirm them in the package composer.json and its test matrix before adopting it. Also check that your application's PHP and Laravel constraints are compatible with the package and its roundly dependencies.
- How do I install roundly-consulting/trading-analytics-for-laravel with Composer?
- Install it as a normal Composer dependency with composer require roundly-consulting/trading-analytics-for-laravel. Because version 1.1.1 aligns to roundly/package-toolkit ^1.3.0 and roundly/enums ^1.1.0, confirm those constraints resolve in your application before committing. Review the package documentation for any configuration or model integration steps.
- What dependencies does Trading Analytics for Laravel require?
- In the 1.1.1 release, the package requires roundly/package-toolkit ^1.3.0 and roundly/enums ^1.1.0, and its dev dependency on roundly/testing is ^1.2.1. These first-party dependencies and their transitive constraints affect Composer resolution. Projects already using the roundly stack will have the least friction.
- Can I use this Laravel trading analytics package without roundly/package-toolkit or roundly/enums?
- The package is not fully self-contained because it pulls in roundly/package-toolkit and roundly/enums. You can install it without already using those packages, but you should evaluate whether its trading metrics and reporting justify adding the roundly dependency family. Legacy applications with pinned constraints should run a dry-run dependency update first.
- Is version 1.1.1 of trading-analytics-for-laravel a breaking change?
- No documented breaking API changes, new features, or deprecations are associated with 1.1.1; it is described as a maintenance release that aligns dependency floors. If you are upgrading from a pre-1.1 version, review the 1.1.0 changes first. Treat it as a patch-level update but still verify Composer resolution and tests.
- How should I upgrade Trading Analytics for Laravel to 1.1.1 safely?
- Work on an isolated branch, run composer update roundly-consulting/trading-analytics-for-laravel --with-dependencies, and execute your full test suite plus static analysis. Do not combine the update with unrelated dependency upgrades. Then smoke-test enum-dependent and toolkit-dependent paths in staging before production.
- What trading performance metrics can I calculate with this Laravel package?
- The package is designed to calculate key trading performance metrics such as win rate, profit/loss, and returns. It also supports tracking and analyzing trades and strategies and generating concise reports for review and comparison. The exact metric APIs should be confirmed in the package documentation.
- How does Trading Analytics for Laravel integrate with existing models and trade data?
- The overview states that it integrates with existing models and data sources through simple configuration, keeping analytics logic organized and reusable. The provided release notes do not document schema requirements or migration steps. Confirm the expected model contracts and configuration keys in the package docs before implementation.
- Is trading-analytics-for-laravel suitable for production dashboards and ongoing maintenance?
- Functional risk for 1.1.1 is low because it is a patch-level maintenance release, but production suitability depends on support ownership, API stability policy, and version coupling to the roundly toolkit. The package's update cadence is gated by upstream toolkit releases, so budget effort to track dependency floors. If this is an internal package, assign a named owner for updates and security patching.
- When should I choose an alternative to Trading Analytics for Laravel?
- If your Laravel application is not already on the roundly stack, adding package-toolkit and enums may be more dependency overhead than the analytics layer warrants. A dedicated analytics package or application-specific queries may fit better when you need broader features or fewer first-party constraints. This package is strongest for teams already using roundly packages and needing lightweight trading metrics and reports.
Weaver
How can I help you explore Laravel packages today?