Skip to content
This repository was archived by the owner on Nov 8, 2024. It is now read-only.

Conversation

klokane
Copy link
Contributor

@klokane klokane commented Oct 8, 2019

closes #749

Ignore enum duplicity if defined inline and later again in members

+ state: processed (enum)
+ Members
    + queued
    + processed
    + done

@klokane klokane requested review from tjanc and kylef October 8, 2019 12:58
@pksunkara
Copy link
Contributor

Looks like a merge conflict.

@kylef
Copy link
Member

kylef commented Oct 16, 2019

@klokane can you rebase this branch to resolve the conflict so we can merge it?

@klokane
Copy link
Contributor Author

klokane commented Oct 16, 2019

rebased

]
}
},
"content": "duplicit value in enumeration"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this warning is correct and shouldn't be removed. The only thing that needed changing is that the "mson example value" of an enum is added to enumerations after all it's nested members are. What do you think?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Although, perhaps it makes better sense to give a warning in the exact opposite example, where we introduce a new type to enumerations because the example does not match any nested type.

@tjanc tjanc merged commit bda1cad into master Oct 17, 2019
@kylef kylef deleted the klokane/issue-749 branch October 17, 2019 13:33
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Duplicit value in enumeration
4 participants