-
Notifications
You must be signed in to change notification settings - Fork 25
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
Refactor redisgraph.js to Typescript #10
base: master
Are you sure you want to change the base?
Conversation
👏 👏 👏 👏 |
I'll be sending more PR's once this is merged |
@gkorland would you prefer just adding the Typescript types instead of the entire code being refactored? |
@DenisCarriere I would prefer not to switch to TypeScript, if we need any special things that will help you TypeScript consume the client please feel free to send another PR |
looks like another one for definitely typed. It's a shame cause I can see they're already getting type errors that you've probably fixed in your refactoring eg #19 |
Thanks, @DenisCarriere. |
Just found redisgraph and this lib and was excited to start using it. Well, fired it up and went For reference this was written 2016 and today I guess most people just expect any serious library to just work for typescript: https://staltz.com/all-js-libraries-should-be-authored-in-typescript.html |
Btw, forking a separate typescript client is probably not a good idea. There are no specific typescript libraries, there are only javascript libraries which provides typescript annotations. If this project does not want to use typescript annotations internally, then it should provide them externally on definetely typed which will then end up published as |
Anything on approving this? |
@jdgamble555 RedisGraph support was moved to node-redis see: https://github.com/redis/node-redis |
Refactor
redisgraph.js
to TypescriptIssue Ref: #5
I was very surprised to see Redis wasn't using Typescript, it's rare to see new libraries built using CommonJS syntax.