Schema validation error codes
This topic explains all the schema validation errors you can encounter when you create a simulation file.
|
Error code |
Description |
|---|---|
|
0 |
The editor doesn’t recognize the error type. |
|
1 |
The value doesn't match any supported options. |
|
2 |
Outdated property or feature. |
|
257 |
A comment started but wasn't closed. |
|
258 |
A string is missing its closing quotes. |
|
259 |
A number is incomplete or incorrectly formatted. |
|
260 |
A Unicode character isn't valid. |
|
261 |
An escape sequence in a string is incorrect. |
|
262 |
A character isn't allowed in this content. |
|
513 |
A property name is missing. |
|
514 |
YAML expected a comma but didn’t find one. |
|
515 |
A colon : in a key-value pair is missing. |
|
516 |
YAML expected a value, but it’s missing. |
|
517 |
A comma or a closing bracket ] is expected in an array. |
|
518 |
A comma or a closing curly bracket } is expected in an object. |
|
519 |
There's an unnecessary comma at the end of a list. |
|
520 |
A key appears more than once in the same object. |
|
521 |
Comments aren’t allowed in this file type. |
|
768 |
The editor couldn’t load or resolve the schema. |