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
{{ message }}
This repository was archived by the owner on Nov 16, 2023. It is now read-only.
The contract XXXX I am using for my API has two similar properties - "IntProperty" and "StringProperty". IntProperty has IgnoreDataMemberAttribute does not have DataMember attribute. StringProperty has an attribute DataMember(Name = "IntProperty").
When trying to generate the OpenAPI documentation from that contract I get the following error:
Adding schema "XXXX" to the schema reference registry failed with the error: Adding schema "XXXX" to the schema reference registry failed with the error: Adding schema "XXXX" to the schema reference registry failed with the error: Adding schema "XXXX" to
the schema reference registry failed with the error: A property with the name "IntProperty" already exists on "XXXX".
So it looks like that the parser ignores IgnoreDataMemberAttribute, and tries to add IntProperty (one from IntProperty and another one from StringProperty) twice and fails there.
Is it an expected behavior, and if yes, what's the workaround?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The contract XXXX I am using for my API has two similar properties - "IntProperty" and "StringProperty". IntProperty has IgnoreDataMemberAttribute does not have DataMember attribute. StringProperty has an attribute DataMember(Name = "IntProperty").
When trying to generate the OpenAPI documentation from that contract I get the following error:
Adding schema "XXXX" to the schema reference registry failed with the error: Adding schema "XXXX" to the schema reference registry failed with the error: Adding schema "XXXX" to the schema reference registry failed with the error: Adding schema "XXXX" to
the schema reference registry failed with the error: A property with the name "IntProperty" already exists on "XXXX".
So it looks like that the parser ignores IgnoreDataMemberAttribute, and tries to add IntProperty (one from IntProperty and another one from StringProperty) twice and fails there.
Is it an expected behavior, and if yes, what's the workaround?
The text was updated successfully, but these errors were encountered: