Pine Script Editor

Purpose & User Intent: This tool provides a Pine Script editor and analyzer for TradingView-like environments. Exact problem solved: writing, validating, and testing Pine Script strategies/indicators offline or in API-assisted workflows. Intended users are quantitative traders, script developers, researchers, and analysts who need versioned code, syntax validation, and backtest summaries without relying solely on the TradingView UI. When to use: during script creation, debugging, or before deployment to a chart. Core capabilities include code intake, version awareness, syntax/semantic checks, and backtest result generation to guide optimization and risk assessment.

Core features include: (required) Pine Script parsing, syntax validation, and version compatibility checks (v4/v5); (required) semantic analysis such as type inference and correct use of built-in functions; (required) import/export of scripts and metadata; (optional/advanced) static code analysis, library resolution, and dependency tracking; (optional/advanced) a local backtester that produces metrics like equity curve, drawdown, and win rate from historical data; (optional/advanced) script profiling and performance hints; (optional) multi-script workspace with version history and rollback; (optional) exportable reports and JSON results for automation. Distinguishing factors include offline editing with an engine that emulates the TradingView compiler to surface errors before run-time, and a structured backtest summary that helps users iterate quickly.

Inputs & Outputs: Inputs include script_name (string, required), code (string, required), pine_version (string, required), chart_symbol (string, optional), timeframe (string, optional), inputs (array of input_config, optional), libraries (array of strings, optional), backtest_settings (object, optional). Outputs include compile_status, errors, backtest_results, and performance_metrics. Algorithms & Calculations describe lexical analysis, syntax parsing, AST generation, semantic checks, version mapping, and a backtester; details align with Pine Script v4/v5 semantics. Error handling covers missing inputs, invalid versions, syntax errors, and large scripts. Assumptions & Exclusions clarify scope beyond UI, including no live trading integration and no front-end rendering.