[WARNING] const math = context.math syntax is deprecated.

[tripolskypetr]

This message appears

[WARNING] const math = context.math syntax is deprecated. Use const { math, ta, input } = context.pine instead. This will be removed in a future version.

When I run

const pine = new PineTS(provider, "BTCUSDT", "1h", 100);
await pine.ready()
pine.run(code)

The code is

//@version=5
indicator("Signal Strategy 100 candles of 1H timeframe")

// Indicators - faster settings for 1H
rsi = ta.rsi(close, 10)
atr = ta.atr(10)
ema_fast = ta.ema(close, 7)
ema_slow = ta.ema(close, 16)

// Conditions
long_cond = ta.crossover(ema_fast, ema_slow) and rsi < 65
short_cond = ta.crossunder(ema_fast, ema_slow) and rsi > 35

// Levels - tighter SL, wider TP for better RR
sl_long = close - atr * 1.5
tp_long = close + atr * 3
sl_short = close + atr * 1.5
tp_short = close - atr * 3

// Plots for extraction
plot(close, "Close")
plot(long_cond ? 1 : short_cond ? -1 : 0, "Signal")
plot(long_cond ? sl_long : sl_short, "StopLoss")
plot(long_cond ? tp_long : tp_short, "TakeProfit")
plot(60, "EstimatedTime")  // 1 hour in minutes

[alaa-eddine]

Thank you for reporting, this due to a legacy transpiler logic that I might've missed.
it should not harm the execution, I'll fix it in the next release.

[alaa-eddine]

oh I just noticed that you don't have any math operation in your indicator, this is weird.
is the the only thing you are doing here ? just passing pine script code to PineTS ? no other indicator running ?

[pegaltier]

Hey, I have noticed the same warning in my unit tests even if I don't find any reference to 'const math = context.math' in my codebase

[alaa-eddine]

@pegaltier the unit test cases are due to a legacy testing function called runNSFunctionWithArgs that was still using context.core, I'll update it.
but I'm not able to reproduce the case reported by @tripolskypetr in an isolated code.

@tripolskypetr is it possible to share your whole code or tell me if you are using it through one of the existing unit tests ?

[tripolskypetr]

It is not just a unit test. I have integrated pinets to the self hosted trading framework with take profit, stop loss, partial profit, trailing stop, breakeven, signal risk rejection, easiest exchange API integration

By the way I am building trading runtime which allows to convert pinets indicator into full fledged trading strategy with backtest, live, paper both. For free as a beer and without 40_000 bars limit

Download this zip and type npm install && npm start. An issue will appear

P.S. This will take a few days to implement profitable strategy with pinets and code the gui. When I finish I will open a discussion with an article which describes how to use this

REPRODUCED.zip

@alaa-eddine
@pegaltier

[alaa-eddine]

@tripolskypetr That's amazing ! I'm looking forward to testing your project, and that's exactly one of PineTS goals : allowing developers like you to run Pine Script in a standalone environment without TradingView constraints.

Thank you for providing the code this will help me identifying the source of the issue.

Also don't hesitate to open a discussion sooner, coz building a long term winning strategy is ... a long term work 😄 usually we under estimate the challenge.

and btw, PineTS will implement Strategy namespace as well, first by mirroring the same capabilities as PineScript but later I'm considering to add more Strategy and backtesting capabilities (like Monte-Carlo testing, biases detections ...etc)

Also Trading capabilities is interesting, but I don't have immediate plans for it, maybe we can collaborate on some features in the future ;)

[tripolskypetr]

The problem of pinescript as a strategy language is it allows you only to use technical analysis instead of fundamentals. For example, you simple can not use LLM to seek for huge sell wall in the order book

Also it require you to think about the math. For example, you will have to calculate breakeven price manually with fees plus slippage every time.

Like that

entryPrice * (1 + commissionPct * 2 + slippagePct * 2)

Or like that

breakeven = entryPrice * (1 + entryFee) / (1 - exitFee - slippage)

Or that

trueBreakeven := entryPrice * (1 + entryCommission) / (1 - exitCommission - slippage) * (1 + fundingRate * holdingPeriod / 8) * ...

Quick advice

All of this should be hidden under the hood of trading framework and be readonly for vibe coders. That means in the case of native pinescript strategies you will have to implement custom standard library (won't be capable for 100% with TradingView so visual debug lost) or take nice comments like this even if an issue is related to number precision

Case is: don't waste the time on strategies, improve the playground. As a benefit, you will catch bugs earlier when they are visualized

By the way I got some code for this. Not sure if this will work

Could you assist?

This will speed up demo stage

Can I delegate the initial strategy implementation to someone from the contributors of pinets so we can backtest the tool even on some kind of timeframe in the past?

Do you have any pinescript indicators which can be used as short/long signals generator right now?

@alaa-eddine
@pegaltier

[alaa-eddine]

@tripolskypetr what you mentioned is also part of the reasons why PineTS exists, and this is why it can use Pine Script source code, but also PineTS syntax which is pure JS code that mimics Pine Script.
in PineTS syntax you can call standard JS functions, which means you can use anything you want to perform your foundamental analysis, market sentiment, LLMs ...etc

Regarding the strategies implementation, I agree that TV have many problems usually reported by the community, but in order to address them, I need to implement compatible interfaces as Pine Script, but the outcome / visualization can be different, and as I said, for example Monte-Carlo testing will be part of it. but we need the base which is 1:1 compatibility to Pine Script, then augment with TypeScript/JavaScript capabilities (just like we said about LLMs)

And btw, the playground will be enhanced, I'm already working on the next version that will improve the code editor with code completion, folding ...etc and probably vibe coding in the future.

Regarding the assistance, I can take a look at what you implemented and provide you with an example indicator. unfortunately I'm still the only maintainer of the project and can't guarantee any commitment atm.

[tripolskypetr]

The problem is an architecture of PineScript itself. An idea to code both trailing stop, breakeven, entry in a single file on exactly the one timeframe is not so good. PineTS got an attempt to solve it, but this is quite fundamental issue in the pinescript language design itself

In a short time I will publish a sample how to split trading strategy into multiple pinets files to keep single responsibility principle. Need an indicator, start date, end date (ok if both in the past), timeframe for a demo, mine goes 50/50

For example, paper trading. Paper trading is a live trading but requests to open OCO order requests not being sent.

As a result

1. Have to code OCO externally each time. If we implement this in pinets source this will affect a bundle size. Bad for web browser visualisation. Yeap can code an interface for this but Alpaca Provider #44

2. When I want to switch from live to paper with command line arguments have to use if condition in the PineScript code itself which makes it non SOLID (gonna be impossible to run on original tradingview without cropping it). The command line argument becomes a side effect for the strategy code

So the priority in my opinion

1. Indicators support (which is already great but got some minor issues like parsing indents in pinescript)

2. IDE (the core is done and published on website, just add more than 500 candles and make this standalone opensource app)

3. Strategies (the last one and is not so important)

Or just ignore this, you known what to do

Btw

Regarding the assistance, I can take a look at what you implemented and provide you with an example indicator. unfortunately I'm still the only maintainer of the project and can't guarantee any commitment atm.

The results are nice, looks like you got a significant experience in pinescript. I think you already got an indicator for this. You can just text it to the comment, I will test it and will adapt it for a strategy

@alaa-eddine

[alaa-eddine]

@tripolskypetr I identified the root cause of these warning messages, I'm preparing a hotfix release.
you mentioned in your last message some indent problems, can you attach an example .pine code where it's happening ? I can probably make a fix for it in the same release.

[tripolskypetr]

The same code. This is not working

//@version=5
indicator("Signal Strategy 15m v1", overlay=true)

plotcandle(open, high, low, close, 
     color=close > open ? color.new(color.green, 70) : color.new(color.red, 70),
     wickcolor=color.new(color.gray, 70),
     bordercolor=color.new(color.gray, 70))


// === INPUTS ===
rsi_len = input.int(7, "RSI Length", minval=2)
ema_fast_len = input.int(5, "EMA Fast", minval=1)
ema_slow_len = input.int(13, "EMA Slow", minval=1)
ema_trend_len = input.int(50, "EMA Trend", minval=1)
atr_len = input.int(14, "ATR Length", minval=1)
vol_ma_len = input.int(20, "Volume MA Length", minval=1)

sl_mult = input.float(1.5, "SL ATR Multiplier", minval=0.5, step=0.1)
tp_mult = input.float(2.5, "TP ATR Multiplier", minval=0.5, step=0.1)
signal_valid_bars = input.int(5, "Signal Valid Bars", minval=1)

// === INDICATORS ===
rsi = ta.rsi(close, rsi_len)
ema_fast = ta.ema(close, ema_fast_len)
ema_slow = ta.ema(close, ema_slow_len)
ema_trend = ta.ema(close, ema_trend_len)
atr = ta.atr(atr_len)

// Volume filter - выше среднего
vol_ma = ta.sma(volume, vol_ma_len)
vol_spike = volume > vol_ma * 1.1

// Momentum confirmation
mom = ta.mom(close, 3)
mom_up = mom > 0
mom_down = mom < 0

// === TREND FILTER ===
trend_up = close > ema_trend and ema_fast > ema_trend
trend_down = close < ema_trend and ema_fast < ema_trend

// === ENTRY CONDITIONS ===
// Long: пересечение + RSI не перекуплен + тренд вверх + объём + momentum
long_cond = ta.crossover(ema_fast, ema_slow) 
     and rsi > 40 and rsi < 65 
     and trend_up 
     and vol_spike 
     and mom_up

// Short: пересечение + RSI не перепродан + тренд вниз + объём + momentum  
short_cond = ta.crossunder(ema_fast, ema_slow) 
     and rsi < 60 and rsi > 35 
     and trend_down 
     and vol_spike 
     and mom_down

// === SIGNAL MANAGEMENT ===
var int bars_since_signal = 0
var int last_signal = 0
var float entry_price = na
var float signal_atr = na

if long_cond
    last_signal := 1
    bars_since_signal := 0
    entry_price := close
    signal_atr := atr
else if short_cond
    last_signal := -1
    bars_since_signal := 0
    entry_price := close
    signal_atr := atr
else
    bars_since_signal += 1

// Signal expires faster on 15m
active_signal = bars_since_signal <= signal_valid_bars ? last_signal : 0

// === DYNAMIC SL/TP based on ATR ===
sl = last_signal == 1 ? entry_price - signal_atr * sl_mult : 
     last_signal == -1 ? entry_price + signal_atr * sl_mult : na
     
tp = last_signal == 1 ? entry_price + signal_atr * tp_mult : 
     last_signal == -1 ? entry_price - signal_atr * tp_mult : na

// === VISUALIZATION ===
line_color = active_signal == 1 ? color.green : active_signal == -1 ? color.red : color.gray

plot(ema_fast, "EMA Fast", color=color.new(color.blue, 50), linewidth=1)
plot(ema_slow, "EMA Slow", color=color.new(color.orange, 50), linewidth=1)
plot(ema_trend, "EMA Trend", color=color.new(color.white, 70), linewidth=2)

plotshape(long_cond, "Long", shape.triangleup, location.belowbar, color.green, size=size.small)
plotshape(short_cond, "Short", shape.triangledown, location.abovebar, color.red, size=size.small)

plot(close, "Active Signal", color=line_color, linewidth=6)

// === OUTPUTS FOR BOT ===
plot(close, "Close", display=display.data_window)
plot(active_signal, "Signal", display=display.data_window)
plot(sl, "StopLoss", display=display.data_window)
plot(tp, "TakeProfit", display=display.data_window)
plot(60, "EstimatedTime", display=display.data_window)  // 1 hour for 15m TF

If you remove extra tabs, spaces, and line breaks, the code works.

//@version=5
indicator("Signal Strategy 15m v1", overlay=true)

plotcandle(open, high, low, close, 
     color=close > open ? color.new(color.green, 70) : color.new(color.red, 70),
     wickcolor=color.new(color.gray, 70),
     bordercolor=color.new(color.gray, 70))


// === INPUTS ===
rsi_len = input.int(7, "RSI Length", minval=2)
ema_fast_len = input.int(5, "EMA Fast", minval=1)
ema_slow_len = input.int(13, "EMA Slow", minval=1)
ema_trend_len = input.int(50, "EMA Trend", minval=1)
atr_len = input.int(14, "ATR Length", minval=1)
vol_ma_len = input.int(20, "Volume MA Length", minval=1)

sl_mult = input.float(1.5, "SL ATR Multiplier", minval=0.5, step=0.1)
tp_mult = input.float(2.5, "TP ATR Multiplier", minval=0.5, step=0.1)
signal_valid_bars = input.int(5, "Signal Valid Bars", minval=1)

// === INDICATORS ===
rsi = ta.rsi(close, rsi_len)
ema_fast = ta.ema(close, ema_fast_len)
ema_slow = ta.ema(close, ema_slow_len)
ema_trend = ta.ema(close, ema_trend_len)
atr = ta.atr(atr_len)

// Volume filter - выше среднего
vol_ma = ta.sma(volume, vol_ma_len)
vol_spike = volume > vol_ma * 1.1

// Momentum confirmation
mom = ta.mom(close, 3)
mom_up = mom > 0
mom_down = mom < 0

// === TREND FILTER ===
trend_up = close > ema_trend and ema_fast > ema_trend
trend_down = close < ema_trend and ema_fast < ema_trend

// === ENTRY CONDITIONS ===
// Long: пересечение + RSI не перекуплен + тренд вверх + объём + momentum
long_cond = ta.crossover(ema_fast, ema_slow) and rsi > 40 and rsi < 65 and trend_up and vol_spike and mom_up

// Short: пересечение + RSI не перепродан + тренд вниз + объём + momentum  
short_cond = ta.crossunder(ema_fast, ema_slow) and rsi < 60 and rsi > 35 and trend_down and vol_spike and mom_down

// === SIGNAL MANAGEMENT ===
var int bars_since_signal = 0
var int last_signal = 0
var float entry_price = na
var float signal_atr = na

if long_cond
    last_signal := 1
    bars_since_signal := 0
    entry_price := close
    signal_atr := atr
else if short_cond
    last_signal := -1
    bars_since_signal := 0
    entry_price := close
    signal_atr := atr
else
    bars_since_signal += 1

// Signal expires faster on 15m
active_signal = bars_since_signal <= signal_valid_bars ? last_signal : 0

// === DYNAMIC SL/TP based on ATR ===
// sl = last_signal == 1 ? entry_price - signal_atr * sl_mult : last_signal == -1 ? entry_price + signal_atr * sl_mult : na
// tp = last_signal == 1 ? entry_price + signal_atr * tp_mult : last_signal == -1 ? entry_price - signal_atr * tp_mult : na

// === STATIC SL/TP for watch strategy ==
sl = last_signal == -1 ? close * 1.02 : close * 0.98
tp = last_signal == -1 ? close * 0.97 : close * 1.03

// === VISUALIZATION ===
line_color = active_signal == 1 ? color.green : active_signal == -1 ? color.red : color.gray

plot(ema_fast, "EMA Fast", color=color.new(color.blue, 50), linewidth=1)
plot(ema_slow, "EMA Slow", color=color.new(color.orange, 50), linewidth=1)
plot(ema_trend, "EMA Trend", color=color.new(color.white, 70), linewidth=2)

plotshape(long_cond, "Long", shape.triangleup, location.belowbar, color.green, size=size.small)
plotshape(short_cond, "Short", shape.triangledown, location.abovebar, color.red, size=size.small)

plot(close, "Active Signal", color=line_color, linewidth=6)

// === OUTPUTS FOR BOT ===
plot(close, "Close", display=display.data_window)
plot(active_signal, "Signal", display=display.data_window)
plot(sl, "StopLoss", display=display.data_window)
plot(tp, "TakeProfit", display=display.data_window)
plot(60, "EstimatedTime", display=display.data_window)  // 1 hour for 15m TF

@alaa-eddine

[alaa-eddine]

Thank you @tripolskypetr , I was able to identify the indent issues.
warning messages and indent issues are all fixed in the latest release (v0.8.5)
I will close this issue after confirmation.

btw, I noticed that your indicator above is not displayed correctly in the playground (the Y axis interval is too large) I don't know if this is due to the plots generated values or a bug in the charting library, I will look at it later

[tripolskypetr]

I notice you are using chunked candle fetch which override standard 1000 candles binance limit

So why don't you increase number of candles in playground?

Also is it possible to implement plotcandle(open, high, low, close, color=close > open ? color.new(color.green, 70) : color.new(color.red, 70), wickcolor=color.new(color.gray, 70), bordercolor=color.new(color.gray, 70))? I really would like to draw my lines on top of candles

@alaa-eddine