You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the schema JSON syntax, if you write { "type": "Entity" } or { "type": "EntityOrCommon" } without a "name" key, this is legal and refers to a common type named Entity or EntityOrCommon respectively. Accordingly, the current error message is
failed to resolve type: Entity
help: `Entity` has not been declared as a common type
While technically correct, this message is not as helpful as it could be; a better help message would suggest that the user needs to add a "name" key. For instance, { "type": "Entity", "name": "User" }.
Describe alternatives you've considered
N/A
Additional context
No response
Is this something that you'd be interested in working on?
👋 I may be able to implement this feature request
⚠️ This feature might incur a breaking change
The text was updated successfully, but these errors were encountered:
Category
Error message improvements
Describe the feature you'd like to request
In the schema JSON syntax, if you write
{ "type": "Entity" }
or{ "type": "EntityOrCommon" }
without a"name"
key, this is legal and refers to a common type namedEntity
orEntityOrCommon
respectively. Accordingly, the current error message isWhile technically correct, this message is not as helpful as it could be; a better help message would suggest that the user needs to add a
"name"
key. For instance,{ "type": "Entity", "name": "User" }
.Describe alternatives you've considered
N/A
Additional context
No response
Is this something that you'd be interested in working on?
The text was updated successfully, but these errors were encountered: