You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: bump README examples to v0.2.0, document Strategy/Backtest
The dependency snippets still pointed at v0.1.0 even though main is on
v0.2.0; bring them in sync. Same for the Maven Central preview line.
Also expand Quick start with a "decomposed" example that uses the v0.2
domain handles directly (compile -> Strategy -> Backtest), update the
Cancellation section with the two cancel paths (future#cancel(true) and
Backtest#cancel()), and refresh the roadmap so v0.2 reflects what
shipped: domain objects + Flow.Publisher progress + hourly Lastra/
Parquet downloads.
job.progress().subscribe(/* a Flow.Subscriber<BacktestProgress> */);
107
+
108
+
ResultMap result = job.await().join();
109
+
```
110
+
111
+
`Backtest` exposes `id()`, `state()`, `progress()` (a `Flow.Publisher<BacktestProgress>`),
112
+
`await()`, and `cancel()` (best-effort server-side `cancelExecution`).
113
+
93
114
## What `backtest()` does
94
115
95
116
Orchestrates the four-step workflow exposed by the raw API:
@@ -151,14 +172,21 @@ try {
151
172
152
173
## Cancellation
153
174
154
-
Cancel the returned `CompletableFuture`to stop polling. If the execute stage has already started server-side, the SDK best-effort calls `cancelExecution` on the backend.
175
+
Two ways to cancel an in-flight backtest:
155
176
156
177
```java
178
+
// 1. Cancel the future returned by the backtest() shortcut.
0 commit comments