FilterErrorType
Identifies the category of a parse or validation error produced by the Studio Explorer filter expression engine.
Items 19
| History | Name | Value | Description | |
|---|---|---|---|---|
| 644 | BackslashNotEscapingAnything | 0 | A backslash at the end of a quoted string has nothing after it to escape. | |
| 644 | BadBespokeFilter | 1 | A recognized bespoke filter keyword (such as | |
| 644 | BadName | 2 | An unexpected token was encountered where a name or identifier was expected. | |
| 644 | IncompleteOr | 3 | Reserved error code for an incomplete | |
| 644 | IncompleteParenthesis | 4 | An opening parenthesis | |
| 644 | InvalidDoubleStar | 5 | A | |
| 644 | InvalidTilde | 6 | A lone | |
| 644 | PropertyBadOperator | 7 | A comparison operator other than | |
| 644 | PropertyDoesNotExist | 8 | The named property does not exist on any reflected class known to the filter engine. | |
| 644 | PropertyInvalidField | 9 | A sub-field index (such as | |
| 644 | PropertyInvalidValue | 10 | The value string provided for a property comparison cannot be parsed into
the expected type for that property (for example, | |
| 644 | PropertyUnsupportedFields | 11 | A sub-field index was used with a property type that does not support
field access (for example, | |
| 644 | PropertyUnsupportedProperty | 12 | The named property exists but its type is not supported by the filter
engine (for example, complex datatypes such as | |
| 644 | UnexpectedNameIndex | 13 | A | |
| 644 | UnexpectedToken | 14 | A token that cannot be a value (such as an operator) appears where a value is expected after a comparison operator. | |
| 644 | UnfinishedBinaryOperator | 15 | An | |
| 644 | UnfinishedQuote | 16 | A quoted string was opened but not closed before the end of the filter input. | |
| 644 | UnknownBespokeFilter | 17 | A | |
| 644 | WildcardInProperty | 18 | A wildcard ( |
Description
FilterErrorType classifies each FilterError returned when the Studio
Explorer filter bar cannot parse or validate a filter expression. A
FilterError carries the type alongside the source range and human-readable
message so tooling can distinguish failure categories programmatically.
Values fall into three groups:
- Lexer errors — the raw character stream cannot be tokenized.
- Parser errors — a valid token stream forms an invalid expression tree.
- Bespoke-filter and property errors — the expression is syntactically valid but semantically incorrect (unknown property, unsupported type, bad operator, and similar).
History 20
- 644 Add WildcardInProperty
- 644 Add UnknownBespokeFilter
- 644 Add UnfinishedQuote
- 644 Add UnfinishedBinaryOperator
- 644 Add UnexpectedToken
- 644 Add UnexpectedNameIndex
- 644 Add PropertyUnsupportedProperty
- 644 Add PropertyUnsupportedFields
- 644 Add PropertyInvalidValue
- 644 Add PropertyInvalidField
- 644 Add PropertyDoesNotExist
- 644 Add PropertyBadOperator
- 644 Add InvalidTilde
- 644 Add InvalidDoubleStar
- 644 Add IncompleteParenthesis
- 644 Add IncompleteOr
- 644 Add BadName
- 644 Add BadBespokeFilter
- 644 Add BackslashNotEscapingAnything
- 644 Add FilterErrorType