errors should include line numbers #289

alexch opened this Issue Dec 8, 2016 · 2 comments


None yet

2 participants

alexch commented Dec 8, 2016

Let's try #283 again.

  1. Debugging syntax errors in RAML files is hard
  2. Line numbers are important for debugging syntax errors
  3. raml2html should tell me the line numbers my errors happen on
  4. raml-js-parser returns a range object which probably includes some line numbers but raml2html prints it as range: [Object] which is not helpful

desired behavior: raml2html prints line numbers with errors


Should be a lot better now by using JSON.stringify. Errors are not processed in any other way.

@alexch alexch referenced this issue in raml-org/raml-js-parser-2 Dec 8, 2016

line numbers are off by one #575

alexch commented Dec 8, 2016

Awesome! This is exactly what I needed. Thanks.

@kevinrenskers kevinrenskers added a commit that referenced this issue Dec 14, 2016
@kevinrenskers kevinrenskers Merge branch 'master' into develop
* master:
  4.0.2: Improve error output (#289)
  4.0.1: documentation fixes, added .nvmrc
  Releasing 3.0.1
  process.exit async, fixes #259 (#260)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment