raml-java-parser-2 icon indicating copy to clipboard operation
raml-java-parser-2 copied to clipboard

Published 20 hours ago • verified publisher icon raml-org

Javascript RAML parser for Java

Open bademux opened this issue 8 years ago • 9 comments

"The parser makes use of Webpack bundled Javascript RAML parser via the Nashorn scripting engine" Please tell me it is proof of concept.

Let me rephrase, Will the official RAML parser for java use Javascript raml parser inside Nashorn?

Thanks

bademux avatar Mar 04 '16 17:03 bademux

You don't have to worry. There will be something native coming.

sichvoge avatar Mar 04 '16 17:03 sichvoge

thanks! I waiting for it, cos the quality of swagger-codegen makes me cry like a baby :(

bademux avatar Mar 04 '16 17:03 bademux

Let me ask more questions about new parser:

  1. Is there ETA?
  2. Do you think about generating parser to JS with GWT's JS Interop
  3. Google`s j2objc allows you to export it to binary library

bademux avatar Mar 05 '16 15:03 bademux

  1. No ETA yet; we'd like to open source our development asap - that version is not GA though, but help our community to see and test our progress.
  2. I don't think so. The JS parser itself will be native.
  3. That probably is a good idea. Question is if that makes sense or not? You can translate something into something else quite often, but that usually comes with some downsides. An y experience with that?

sichvoge avatar Mar 06 '16 09:03 sichvoge

And I hope the last one: Will RAML java parser v8 be compatible with v1?

Let me explain my curiosity. I'm choosing standard (and tooling) for my project. Native tools (JS for javascript, binary for iOS devs, java for Android) can make them happy (faster builds, better tooling integration) without rewriting tooling. So potentially I'm interested, just need more information about the project. Thanks!

bademux avatar Mar 06 '16 17:03 bademux

regarding v08 and v1 compatibility, the same parser will be able to parse both spec versions, though it will return objects that implement the interfaces for their respective version

svacas avatar Mar 07 '16 21:03 svacas

Hi, thanks again for the clarification! One more question:

How issues for v0.8 will be solved?

Found some architectural (I believe) problems with v0.8 parser here and here. Will it done right for 1.0 or legacy implementation will be fixed too ?

bademux avatar Mar 09 '16 16:03 bademux

All the current parser issues will be reviewed on the new parser implementation

svacas avatar Mar 09 '16 19:03 svacas

Please use the following link for the alpha version of the native Java parser. This repo will be deprecated soon.

sichvoge avatar May 10 '16 07:05 sichvoge