title: CodeError
'@id': stencila:CodeError
extends: Entity
role: secondary
status: unstable
category: code
description: An error that occured when parsing, compiling or executing some Code.
properties:
  errorType:
    '@id': stencila:errorType
    description: The type of error.
    type: string
  message:
    '@id': stencila:errorMessage
    description: The error message or brief description of the error.
    type: string
  trace:
    '@id': stencila:trace
    description: Stack trace leading up to the error.
    type: string
required:
  - message

title: CodeError
'@id': stencila:CodeError
extends: Entity
role: tertiary
status: unstable
category: code
description: An error that occurred when parsing, compiling or executing a Code node.
properties:
  errorType:
    '@id': stencila:errorType
    description: The type of error e.g. "SyntaxError", "ZeroDivisionError".
    $comment: |
      Many languages have the concept of alternative types of errors.
      For example, Python has various [classes of exceptions](https://docs.python.org/3/tutorial/errors.html).
      This property is intended to be used for storing these type names as additional
      information that maybe useful to the user attempting to resolve the error.
    type: string
  errorMessage:
    '@id': stencila:errorMessage
    aliases:
      - message
    description: The error message or brief description of the error.
    type: string
  stackTrace:
    '@id': stencila:stackTrace
    aliases:
      - trace
    description: Stack trace leading up to the error.
    type: string
required:
  - message

Modify prop names; errorType comment
fix(CodeError): Modify prop names; errorType comment

The property names `message` and `trace` have a higher chance of clashing with e.g. schema.org in the future. Also `errorMessage` is more consistent with `errorType`.