Merged
Conversation
Fix : PineScript User defined types were not correctly transpiled from pine script source
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added
Indicatorclass to pass custom input values at runtime. Create indicators withnew Indicator(source, inputs)and pass them toPineTS.run(). Input values override default values frominput.*declarations.input.*namespace methods to resolve values from runtime inputs viacontext.inputs, falling back to default values when not provided.Fixed
typekeyword) now correctly transpile toType({...})syntax instead of JavaScript classes, ensuring compatibility with PineTS runtime.