-
Notifications
You must be signed in to change notification settings - Fork 192
(Trade) Arrows with Optional Annotations #157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
}) | ||
|
||
pluginName <- "Arrow" | ||
if (dyHasPlugin(dygraph, pluginName)) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This behavior could just be made part of dyPlugin
(i.e. if an a plugin name that already exists in the dygraph is added then we append rather than overwrite options). Would there be any downsides to this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense. I'm going to make a separate pull request introducing changes in dyPlugin
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR added #158
I think this looks very cool and seems extremely useful! |
I've made some significant improvements to this plugin. Now it's ready to be released. The updated version can be reached at http://work.severus.io/dygraphs/ |
I'm creating this pull request to gather some feedback on (Trade) Arrows with Optional Annotations feature I'm currently working on.
The output of the current implementation is available here: http://work.severus.io/dygraphs/
@jjallaire @danielkrizian what do you think of it?