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
Copy file name to clipboardExpand all lines: graph/patterns/dictionary.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ For more information, see the [OData reference](https://github.com/oasis-tcs/oda
41
41
The following example demonstrates defining a dictionary that can contain string values.
42
42
43
43
```xml
44
-
<SchemaNamespace="microsoft.graph">
44
+
<SchemaNamespace="microsoft.graph"><!--NOTE: the namespace that declares the Dictionary complex type *must* be microsoft.graph-->
45
45
<ComplexTypeName="Dictionary"OpenType="true">
46
46
<AnnotationTerm="Core.Description"String="A dictionary of name-value pairs. Names must be valid property names, values may be restricted to a list of types via an annotation with term `Validation.OpenPropertyTypeConstraint`." />
47
47
</ComplexType>
@@ -119,8 +119,7 @@ Dictionaries can also contain complex types whose values may be constrained to a
119
119
The following example defines a complex type **roleSettings**, an **assignedRoleGroupDictionary** that contains **roleSettings**, and an **assignedRoles** property that uses the dictionary..
120
120
121
121
```xml
122
-
123
-
<SchemaNamespace="microsoft.graph">
122
+
<SchemaNamespace="microsoft.graph"> <!--NOTE: the namespace that declares the Dictionary complex type *must* be microsoft.graph-->
124
123
<ComplexTypeName="Dictionary"OpenType="true">
125
124
<AnnotationTerm="Core.Description"String="A dictionary of name-value pairs. Names must be valid property names, values may be restricted to a list of types via an annotation with term `Validation.OpenPropertyTypeConstraint`." />
0 commit comments