Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

igluctl: Raise errors in parseable errorformat #500

Open
mrchief opened this issue Mar 21, 2020 · 0 comments
Open

igluctl: Raise errors in parseable errorformat #500

mrchief opened this issue Mar 21, 2020 · 0 comments

Comments

@mrchief
Copy link

mrchief commented Mar 21, 2020

Igluctl lint reports errors that are spread over multiple lines and look something like this

Cannot read [com.test]: no valid JSON SchemasCannot parse [com.test/test_schema/jsonschema/1-0-0]: Unexpected character ('}' (code 125)): was expecting double-quote to start field name
 at [Source: {
  "$schema": "http://iglucentral.com/schemas/com.snowplowanalytics.self-desc/schema/jsonschema/1-0-0#",
  "description": "Test.",
  "self": {
    "vendor": "com.test",
    "name": "test_schema",
    "format": "jsonschema",
    "version": "1-0-0"
  },
  "type": "object",
  "properties": {

    "prop": {
      "description": "Test prop",
      "enum": ["test"]
    },

  },
  "minProperties": 1,
  "required": [
    "prop"
  ],
  "additionalProperties": false
}
; line: 18, column: 4]

It'd be great if the error could be formatted in {file}:{line}:{column}: {message} format. I'm building a lint action to validate and report errors on Github Pull Requests. Having errors output in this format opens up numerous possibilities like annotations and file suggestions.

@mrchief mrchief changed the title Raise errors in parseable errorformat igluctl: Raise errors in parseable errorformat Mar 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant