We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Validating a schema that has out-of-line annotations targeting an enum member fails.
OData .Net lib 7.6-beta.
load and validate the following schema:
<edmx:Edmx Version="4.0" xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx"> <edmx:Reference Uri="https://oasis-tcs.github.io/odata-vocabularies/vocabularies/Core.xml"> <edmx:Include Namespace="Org.OData.Core.V1" Alias="Core"/> </edmx:Reference> <edmx:DataServices> <Schema Namespace="my.ns" Alias="myns" xmlns="http://docs.oasis-open.org/odata/ns/edm"> <EnumType Name="MyEnum"> <Member Name="MyMember" Value="0"/> </EnumType> <Annotations Target="myns.MyEnum/MyMember"> <Annotation Term="Core.Description" String="This is an annotation"/> </Annotations> </Schema> </edmx:DataServices> </edmx:Edmx>
Successful validation
Error: The property "MyMember" could not be found. Location (12, 10)
odata.net/src/Microsoft.OData.Edm/Csdl/Semantics/CsdlSemanticsVocabularyAnnotation.cs
Line 198 in ba32541
The text was updated successfully, but these errors were encountered:
4c5d797
Fix OData#1465
eda4ab1
Support validating out-of-line annotations target enum member.
Fix #1465
0d7328e
No branches or pull requests
Validating a schema that has out-of-line annotations targeting an enum member fails.
Assemblies affected
OData .Net lib 7.6-beta.
Reproduce steps
load and validate the following schema:
Expected result
Successful validation
Actual result
Error: The property "MyMember" could not be found. Location (12, 10)
Additional detail
odata.net/src/Microsoft.OData.Edm/Csdl/Semantics/CsdlSemanticsVocabularyAnnotation.cs
Line 198 in ba32541
The text was updated successfully, but these errors were encountered: