user-defined types (UDTs) support?

[jwernisch]

First off, great runtime! Most of the initial pineScripts we tested work as expected.

However, I am having some issues with more complex scripts. It seems I am unable to create an instance of the UDT or assign values. Using a stripped down example, the code below results in a TypeError: Settings.new is not a function error:

type Settings
float source

Settings settings =
Settings.new(
input.source(title='Source', defval=close, group="General Settings", tooltip="Source of the input data")
)

Are UDTs currently supported (v0.7.3) or am I doing something incorrectly?
Is there an alternative way to write this code? Any documentation that I am missing?

Thanks!

[alaa-eddine]

Hi @jwernisch
Thank you for reporting this.
and I confirm that UDTs are not supported yet, you're not doing anything wrong.
They are pretty challenging because they require specific transpiling logic : UDTs in PineScript are different from types in TypeScript, so the idea is to convert them to dynamic class declarations...

Starting from PineTS v0.7.0+ the goal becomes PineScript parity and ability to run PineScript source directly, user defined types are in the roadmap, but I still didn't find time to tackle them, as I'm working on some remaining core API methods/constants + plots.

[jwernisch]

No problem, I figured it may be a long shot. You are progressing the runtime quite quickly, excited to see what improvements are in store for the future.

[alaa-eddine]

The ultimate goal is to build a full quant ecosystem, with indicators, charting (via QFChart), backtesting, and probably even trading libraries.

In this context, what are you main use cases / tests of PineTS ? and what future features you'll be interested in ?