You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Igor Sapego (JIRA)" <ji...@apache.org> on 2019/01/23 10:41:00 UTC
[jira] [Commented] (IGNITE-11032) Typescript for Node.js Client
[ https://issues.apache.org/jira/browse/IGNITE-11032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749795#comment-16749795 ]
Igor Sapego commented on IGNITE-11032:
--------------------------------------
[~thavlik], there is a public [TeamCity|https://cwiki.apache.org/confluence/display/IGNITE/Continuous+Integration], that you can use to test your patch if you can not run tests locally.
Also, if there is a problem with tests it's a good reason to send a message to a devlist - maybe we need to improve comething here.
Can you create a Pull Request for your improvement, so it's easier to review and run tests over it?
> Typescript for Node.js Client
> -----------------------------
>
> Key: IGNITE-11032
> URL: https://issues.apache.org/jira/browse/IGNITE-11032
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
> Reporter: Thomas Havlik
> Priority: Major
>
> So I've started doing this today. My goal is to complete this work quickly so it has a good chance of being merged. I've found it difficult to find whoever the right person would be to get started on this.
> [https://github.com/thavlik/ignite]
> Note that I can't get the tests to run because my computer is having issues running Ignite locally, and I have no intention of moving the tests to Typescript. Only the imports for the tests will be changing.
> Also, I am removing all default exports as per its numerous caveats: [https://blog.neufund.org/why-we-have-banned-default-exports-and-you-should-do-the-same-d51fdc2cf2ad]
> Edit: I am able to confirm the Typescript client is a working drop-in replacement for my app after changing the imports.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)