This repository has been archived by the owner on Nov 8, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 54
Duplicit value in enumeration #749
Labels
Comments
Hi @sixeyes, I think this looks like a bug in the parser (Drafter). Thank you for reporting, we'll debug this further and get the the bottom of the problem, for now I think you can ignore these warnings in your document. |
Parse Result: {
"element": "enum",
"attributes": {
"enumerations": {
"element": "array",
"content": [
{
"element": "string",
"attributes": {
"typeAttributes": {
"element": "array",
"content": [
{
"element": "string",
"content": "fixed"
}
]
}
},
"content": "Processed"
},
{
"element": "string",
"meta": {
"description": {
"element": "string",
"content": "The wave has been created but not queued."
}
},
"attributes": {
"typeAttributes": {
"element": "array",
"content": [
{
"element": "string",
"content": "fixed"
}
]
}
},
"content": "Draft"
},
{
"element": "string",
"meta": {
"description": {
"element": "string",
"content": "The wave has been queued but not processed."
}
},
"attributes": {
"typeAttributes": {
"element": "array",
"content": [
{
"element": "string",
"content": "fixed"
}
]
}
},
"content": "Queued"
}
]
}
},
"content": {
"element": "string",
"attributes": {
"typeAttributes": {
"element": "array",
"content": [
{
"element": "string",
"content": "fixed"
}
]
}
},
"content": "Processed"
}
}
} Actual:
Expectation:
|
Merged
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I've been busy with other projects for the last few months but returned to work on my API docs and discovered I now have 16 semantic errors, even though I've not changed the document. The errors are all:
Duplicit value in enumeration
Line xxxx API Blueprint
They all refer to enumerations declared in Data Structures section
The error line xxxx in this example refers to the
+ status:
line. If I remove theProcessed
value I get an error indicating I've not supplied a value.At the moment it's just a semantic error, but I'd like to know what's changed and what I can do to fix the warnings.
The text was updated successfully, but these errors were encountered: