-
Notifications
You must be signed in to change notification settings - Fork 123
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
Future of project / v2 #75
Comments
For those who want to follow along, I'll be working at https://github.com/gadicc/node-yahoo-finance2. DO NOT USE "yahoo-finance2" (above repo) FOR ANYTHING. "yahoo-finance2" is all experimentation. There is no timetable. Thanks everyone :) |
In case anyone is following here, would love some feedback on what's done so far. The TypeScript support is really great, e.g.: There's a live demo at https://codesandbox.io/s/yahoo-finance2-312x2?file=/src/index.ts. |
@gadicc Hey man, I'm just trying out |
Thanks, @pudgereyem, that would be great. The current E.g. |
@gadicc Sorry for not checking and sharing feedback earlier. I meant to do a TS rewrite for years but it never happened. I have just invited you as collaborator to this repo and also added you as owner for yahoo-finance npm package. Once your TS version development is completed, please consider publishing to |
Hey @pilwon! All good, my dear friend. Truuuuust me, I know all about having a busy life and then getting endless GitHub notifications for old open source projects. As you saw, I've wanted to do work more work here for years too, and finally had some time for it now and wanted to give back. Thanks so much, that sounds awesome! I've been careful to be very clear to everyone that this is a beta release and only for people who want to help out with development, and that anyone else should remain using the current I'll just add that I put in a lot of effort to make the project highly maintainable from the beginning and it's really paid off! It's still just the beginning and already so many PRs have come in, including some notable contributions from @pudgereyem and @PythonCreator27. Current pain point is the runtime validation of data we get from Yahoo, to make sure the TypeScript interfaces are correct... I've kept it a little strict to make sure the user gets predictable results, which is resulting in some short term pain now but I think will be well worth it for the rest of the life of the library. Any comments you may have on anything will always be welcome. |
@gadicc This project would have died a long time ago without your PRs :) Now with all these new retail investors flown into the stock market and also the wide adoption of TypeScript, many developers could benefit from our work put into |
Thanks @pilwon you're very kind :) Yes it's interesting times! I see someone is already using the package to show stocks on his TV... which stocks? GME, NOK and BB 😅 As for TypeScript, it's actually my very first time using it, and it rocks (after all the initial learning pain, of course). Thanks, that would be awesome! Whenever the timing is right 🙌 |
TL;DR;
Hey @pilwon
I've been giving some thought as to some changes I'd like to make moving forward, which I'll detail below. I don't really want to do anything on the current version since things have been stable for years. I'd love to hear your thoughts and feelings about your intention for the future of the project and how these relate, e.g.
Depending on your thoughts on the above, I could either start a new repo of my own, or we could do a new branch here if you'd like to add me as maintainer and are ok with all the automation.
To be honest though, I think I'd like to start from scratch and play around a bit, without worrying about backwards compatibility or maintaining the existing code patterns. To that end, I may well just start a new repo and see what develops. Once it becomes stable, we could decide what to do.
Just wanted to give you a heads up and hear your thoughts. Not even sure when I'll even have time to work on this, but wanted to get a feel for things. Thanks and hope all's well your side! :)
The text was updated successfully, but these errors were encountered: