Skip to content
This repository has been archived by the owner on Feb 12, 2022. It is now read-only.

Javascript RAML parser for Java #18

Open
bademux opened this issue Mar 4, 2016 · 9 comments
Open

Javascript RAML parser for Java #18

bademux opened this issue Mar 4, 2016 · 9 comments

Comments

@bademux
Copy link

bademux commented Mar 4, 2016

"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 bademux changed the title Javascript parser for Java Javascript RAML parser for Java Mar 4, 2016
@sichvoge
Copy link
Contributor

sichvoge commented Mar 4, 2016

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

@bademux
Copy link
Author

bademux commented Mar 4, 2016

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

@bademux
Copy link
Author

bademux commented Mar 5, 2016

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

@sichvoge
Copy link
Contributor

sichvoge commented Mar 6, 2016

  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?

@bademux
Copy link
Author

bademux commented Mar 6, 2016

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!

@svacas
Copy link
Collaborator

svacas commented Mar 7, 2016

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

@bademux
Copy link
Author

bademux commented Mar 9, 2016

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 ?

@svacas
Copy link
Collaborator

svacas commented Mar 9, 2016

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

@sichvoge
Copy link
Contributor

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants