Re: [wtp-dev] Fwd: [epp-dev] Neon RC2 packages

["Michael Rennie" <Michael_Rennie@xxxxxxxxxx>]

Eugene,

Our initial tests so far has been around fleshing out the protocol - how it compares to what we already do in Orion and how we can adapt. As we go through the API / protocol / etc, we are planning to open PR's to help improve the documentation (for completeness, etc).

> I believe that writing test cases using java2typescript for example might be a good starting point. They can
> * help to understand the API
> * show whether we need some additional layer on .ts side or not
> * give some benchmarks which are especially important in cases of transferring real AST from JS to Java for example
> * demonstrate difference between running services.ts in separate Node process, Nashorn, J2V8 or Node4J.
> (I like J2V8 and Node4J and I in my opinion it's worth looking at. (java2typescript uses J2V8))
> * be as part JSDT tests later

We are currently running our tests against orion.eclipse.org (which is running the experimental node-based server) - the 'running in a separate node process' scenario.

Michael Rennie

Eugene Melekhov ---15/06/2016 10:14:22 AM---Michael, > Perhaps we could discuss this more on the next JSDT call? It feels to me like there might

From: Eugene Melekhov <emvv@xxxxxxx>
To: "General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
Date: 15/06/2016 10:14 AM
Subject: Re: [wtp-dev] Fwd: [epp-dev] Neon RC2 packages
Sent by: wtp-dev-bounces@xxxxxxxxxxx

---

Michael,

> Perhaps we could discuss this more on the next JSDT call? It feels to me like there might be some overlap work here
> with Orion and JSDT both trying to implement / integrate the services.

Unfortunately TypeScript code is poorly documented. None of the LanguageService interface function is documented, so
it's hard to judge whether LanguageService is enough for our needs and what the common denominator for different
projects like Orion/JSDT could be.

I believe that writing test cases using java2typescript for example might be a good starting point. They can
  * help to understand the API
  * show whether we need some additional layer on .ts side or not
  * give some benchmarks which are especially important in cases of transferring real AST from JS to Java for example
  * demonstrate difference between running services.ts in separate Node process, Nashorn, J2V8 or Node4J.
   (I like J2V8 and Node4J and I in my opinion it's worth looking at. (java2typescript uses J2V8))
  * be as part JSDT tests later

>> Language Service protocol doesn't provide AST which may be necessary to display outline for example.
>> Another point to consider is refactoring which depends on AST as well. Perhaps it makes sense to create some .ts layer
>> between JSDT and TS Services.

> Is this something that could be 'fixed' via an extension to the services?

It depends, perhaps no additional layer is needed depending on tests above.


-- 
Eugene Melekhov

_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev