added types for technical indicator names - #115
Merged
Conversation
Owner
|
I am not sure if passing |
Contributor
Author
|
Yep, it works for me. |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I know this is probably not 100% correctly implemented, but I am using these indicator types and a global.d.ts override and it works well for me.
I saw someone a long time ago suggest proper method signatures so the appropriate indicator also enforces its own appropriate arguments... but this can take some of the edge off for now.
If you can tweak and squeeze this one in, I can extend maybe with the above when I get some time.
Thoughts?