What Lipi does not do
Some names look as though they ought to work, and do not.
Read this page before you spend an afternoon on a script that was never going to resolve.
Names that do not resolve
| Written | What Lipi has |
|---|---|
a declaration opening var or varip | static is the keyword that makes a value persist across bars |
syminfo.tickerid | syminfo.ticker |
barstate.isconfirmed | not present |
| a gradient colour helper, or a separate transparency function | not present; use color.new to set the opacity of a colour you already have |
Punctuation and operators
Statements are separated by newlines. A semicolon is not a statement separator, and source that uses one as a separator does not parse.
There is no exponentiation operator. Source that uses one does not parse, so the failure arrives when you check the script rather than while it runs.
Comments run to the end of a line. There is no block-comment form.
Not part of the v1 surface
Arrays are not part of the v1 language. No array library, type or function is exposed, and the array diagnostics cannot be reached from a script.
Eight further orderflow names are not part of the v1 language and cannot be used.
Categories that do not exist at all
Lipi produces chart indicators. There is no strategy construct, no way to place an order from a script, and no way to request another symbol’s data.
What does work
A complete script, built only from names Lipi has, looks like this:
indicator("Cumulative delta")
plot(orderflow.cvd())