TheCookieLab

Yes, whenever we make breaking changes we need to do a cost benefit analysis of sorts to determine if the improvement outweighs the cost. While updating references isn't a big...

Regarding your builder example, the Strategy should only need to know about its two Rules and not the Indicators they use. An Indicator knows it's own unstable period. If we...

See https://github.com/ta4j/ta4j/issues/947

You'll have to be a bit more descriptive than that on what you're trying to do. On Thu, May 9, 2024 at 7:52 AM Freeongoo ***@***.***> wrote: > I would...

The TradingRecord currently only supports one open position at a time. To do something like what you're proposing you'll need to orchestrate multiple TradingRecords as appropriate. On Thu, May 9,...

Since there has been no activity in this issue for months I'm closing with the assumption the question was answered. If that's not the case feel free to re-open with...

I'm not terribly familiar with this indicator. So hypothetically what would be your ideal alternative - just explicitly passing in a high and low value instead of PivotPointIndicator or something...

> OK, but before I need too many changes, is `ChangeIndicator` fine? Then I'll adapt and rename `ClosePriceDifferenceIndicator`. Yes, everything else is fine.

@Cypher01 are you still planning on making these changes or should I run with it?

> Source data coming is JSON and I'm using Chronicle Wire with an object pool for JSON objects to prevent GC and memory growth there, too ;) > > Let...