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

parser can only handle absolute paths to a raml definition file #11

Open
mutsys opened this issue Dec 12, 2015 · 4 comments
Open

parser can only handle absolute paths to a raml definition file #11

mutsys opened this issue Dec 12, 2015 · 4 comments

Comments

@mutsys
Copy link

mutsys commented Dec 12, 2015

passing anything other than an absolute path to a raml file results in errors in the bundled javascript

this path reliably fails:

src/main/raml/example.raml

with the following exception:

javax.script.ScriptException: TypeError: null has no such function "isTopLevel" in <eval> at line number 4942

this path reliably fails:

~/raml/raml-1/src/main/raml/example.raml

with the following exception:

javax.script.ScriptException: TypeError: null has no such function "title" in <eval> at line number 97

the following path reliably succeeds:

/Users/mrose/raml/raml-1/src/main/raml/example.raml
@sichvoge
Copy link
Contributor

Hi @mutsys, this parser is a wrapper for the JS parser and we realised that there are couple of problems going this root. Therefore, we decided to implement a native Java parser which we will have a beta in a couple of weeks. stay tuned

@jschamburger
Copy link

Hi @sichvoge, are there any news on this? I'd love to get my hands on the new Java parser. :-)

@sichvoge
Copy link
Contributor

Yes, we are currently finalising the alpha version, fixing couple of functional bugs, doing some refactoring, and soon publishing it. I will let you know where we are by the end of this week.

@jschamburger
Copy link

Great, thanks. Looking forward to it!

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