-
Notifications
You must be signed in to change notification settings - Fork 43
/
Resources.resx
366 lines (355 loc) · 22.4 KB
/
Resources.resx
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
<?xml version="1.0" encoding="utf-8"?>
<root>
<!--
Microsoft ResX Schema
Version 2.0
The primary goals of this format is to allow a simple XML format
that is mostly human readable. The generation and parsing of the
various data types are done through the TypeConverter classes
associated with the data types.
Example:
... ado.net/XML headers & schema ...
<resheader name="resmimetype">text/microsoft-resx</resheader>
<resheader name="version">2.0</resheader>
<resheader name="reader">System.Resources.ResXResourceReader, System.Windows.Forms, ...</resheader>
<resheader name="writer">System.Resources.ResXResourceWriter, System.Windows.Forms, ...</resheader>
<data name="Name1"><value>this is my long string</value><comment>this is a comment</comment></data>
<data name="Color1" type="System.Drawing.Color, System.Drawing">Blue</data>
<data name="Bitmap1" mimetype="application/x-microsoft.net.object.binary.base64">
<value>[base64 mime encoded serialized .NET Framework object]</value>
</data>
<data name="Icon1" type="System.Drawing.Icon, System.Drawing" mimetype="application/x-microsoft.net.object.bytearray.base64">
<value>[base64 mime encoded string representing a byte array form of the .NET Framework object]</value>
<comment>This is a comment</comment>
</data>
There are any number of "resheader" rows that contain simple
name/value pairs.
Each data row contains a name, and value. The row also contains a
type or mimetype. Type corresponds to a .NET class that support
text/value conversion through the TypeConverter architecture.
Classes that don't support this are serialized and stored with the
mimetype set.
The mimetype is used for serialized objects, and tells the
ResXResourceReader how to depersist the object. This is currently not
extensible. For a given mimetype the value must be set accordingly:
Note - application/x-microsoft.net.object.binary.base64 is the format
that the ResXResourceWriter will generate, however the reader can
read any of the formats listed below.
mimetype: application/x-microsoft.net.object.binary.base64
value : The object must be serialized with
: System.Runtime.Serialization.Formatters.Binary.BinaryFormatter
: and then encoded with base64 encoding.
mimetype: application/x-microsoft.net.object.soap.base64
value : The object must be serialized with
: System.Runtime.Serialization.Formatters.Soap.SoapFormatter
: and then encoded with base64 encoding.
mimetype: application/x-microsoft.net.object.bytearray.base64
value : The object must be serialized into a byte array
: using a System.ComponentModel.TypeConverter
: and then encoded with base64 encoding.
-->
<xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
<xsd:import namespace="http://www.w3.org/XML/1998/namespace" />
<xsd:element name="root" msdata:IsDataSet="true">
<xsd:complexType>
<xsd:choice maxOccurs="unbounded">
<xsd:element name="metadata">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="value" type="xsd:string" minOccurs="0" />
</xsd:sequence>
<xsd:attribute name="name" use="required" type="xsd:string" />
<xsd:attribute name="type" type="xsd:string" />
<xsd:attribute name="mimetype" type="xsd:string" />
<xsd:attribute ref="xml:space" />
</xsd:complexType>
</xsd:element>
<xsd:element name="assembly">
<xsd:complexType>
<xsd:attribute name="alias" type="xsd:string" />
<xsd:attribute name="name" type="xsd:string" />
</xsd:complexType>
</xsd:element>
<xsd:element name="data">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
<xsd:element name="comment" type="xsd:string" minOccurs="0" msdata:Ordinal="2" />
</xsd:sequence>
<xsd:attribute name="name" type="xsd:string" use="required" msdata:Ordinal="1" />
<xsd:attribute name="type" type="xsd:string" msdata:Ordinal="3" />
<xsd:attribute name="mimetype" type="xsd:string" msdata:Ordinal="4" />
<xsd:attribute ref="xml:space" />
</xsd:complexType>
</xsd:element>
<xsd:element name="resheader">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
</xsd:sequence>
<xsd:attribute name="name" type="xsd:string" use="required" />
</xsd:complexType>
</xsd:element>
</xsd:choice>
</xsd:complexType>
</xsd:element>
</xsd:schema>
<resheader name="resmimetype">
<value>text/microsoft-resx</value>
</resheader>
<resheader name="version">
<value>2.0</value>
</resheader>
<resheader name="reader">
<value>System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
</resheader>
<resheader name="writer">
<value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
</resheader>
<data name="CircularBaseSchemaSet" xml:space="preserve">
<value>Found a type set '{0}' which is circularly defined.</value>
</data>
<data name="EmptyClientName" xml:space="preserve">
<value>Empty x-ms-client-name property.</value>
</data>
<data name="InvalidDefault" xml:space="preserve">
<value>The default value is not one of the values enumerated as valid for this element.</value>
</data>
<data name="UnknownFormat" xml:space="preserve">
<value>'{0}' is not a known format.</value>
</data>
<data name="CircularReference" xml:space="preserve">
<value>Circular reference detected: {0}</value>
</data>
<data name="DefinitionDoesNotExist" xml:space="preserve">
<value>Reference specifies the definition {0} that does not exist.</value>
</data>
<data name="DuplicateOperationIdException" xml:space="preserve">
<value>Found operation objects with duplicate operationId '{0}'. OperationId must be unique among all operations described in the API.</value>
</data>
<data name="ErrorParsingSpec" xml:space="preserve">
<value>Error parsing swagger file</value>
</data>
<data name="ExceededMaximumReferenceDepth" xml:space="preserve">
<value>Reached Maximum reference depth when resolving reference '{0}'.</value>
</data>
<data name="AnonymousTypesDiscouraged" xml:space="preserve">
<value>Inline/anonymous models must not be used, instead define a schema with a model name in the "definitions" section and refer to it. This allows operations to share the models.</value>
</data>
<data name="SecurityDefinitionsStructureValidation" xml:space="preserve">
<value>Every swagger/configuration must have a security definitions section and it must adhere to the structure described in: https://github.com/Azure/azure-openapi-validator/blob/master/docs/security-definitions-structure-validation.md</value>
</data>
<data name="MsdnReferencesDiscouraged" xml:space="preserve">
<value>For better generated code quality, remove all references to "msdn.microsoft.com".</value>
</data>
<data name="APIVersionFormatIsNotValid" xml:space="preserve">
<value>API Version must be in the format: yyyy-MM-dd, optionally followed by -preview, -alpha, -beta, -rc, -privatepreview.</value>
</data>
<data name="HttpVerbIsNotValid" xml:space="preserve">
<value>Permissible values for HTTP Verb are delete,get,put,patch,head,options,post. </value>
</data>
<data name="RequiredReadOnlyPropertiesValidation" xml:space="preserve">
<value>Property '{0}' is a required property. It should not be marked as 'readonly'.</value>
</data>
<data name="ResourceModelIsNotValid" xml:space="preserve">
<value>Model definition '{0}' must have the properties 'name', 'id' and 'type' in its hierarchy and these properties must be marked as readonly.</value>
</data>
<data name="ResourceIsMsResourceNotValid" xml:space="preserve">
<value>A 'Resource' definition must have x-ms-azure-resource extension enabled and set to true.</value>
</data>
<data name="XmsClientNameInvalid" xml:space="preserve">
<value>Value of 'x-ms-client-name' cannot be the same as '{0}' Property/Model.</value>
</data>
<data name="MissingDescription" xml:space="preserve">
<value>{0} lacks 'description' property. Consider adding a 'description' element. Accurate description is essential for maintaining reference documentation.</value>
</data>
<data name="MissingSummaryDescription" xml:space="preserve">
<value>{0} lacks 'description' and 'summary' property. Consider adding a 'description'/'summary' element. Accurate description/summary is essential for maintaining reference documentation.</value>
</data>
<data name="MissingTitleDescription" xml:space="preserve">
<value>{0} lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation.</value>
</data>
<data name="OnlyOneUnderscoreAllowedInOperationId" xml:space="preserve">
<value>Only 1 underscore is permitted in the operation id, following Noun_Verb conventions.</value>
</data>
<data name="OperationIdMissing" xml:space="preserve">
<value>OperationId is required for all operations. Please add it for '{0}' operation of '{1}' path.</value>
</data>
<data name="XMSPathBaseNotInPaths" xml:space="preserve">
<value>Paths in x-ms-paths must overload a normal path in the paths section, i.e. a path in the x-ms-paths must either be same as a path in the paths section or a path in the paths sections followed by additional parameters.</value>
</data>
<data name="DescriptionNotDescriptive" xml:space="preserve">
<value>The value provided for description is not descriptive enough. Accurate and descriptive description is essential for maintaining reference documentation.</value>
</data>
<data name="OperationIdNounInVerb" xml:space="preserve">
<value>Per the Noun_Verb convention for Operation Ids, the noun '{0}' should not appear after the underscore. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.</value>
</data>
<data name="NonAppJsonTypeNotSupported" xml:space="preserve">
<value>Only 'application/json' content-type is supported by ARM.</value>
</data>
<data name="SupportedSchemesWarningMessage" xml:space="preserve">
<value>Azure Resource Management only supports HTTPS scheme.</value>
</data>
<data name="OperationParametersNotAllowedMessage" xml:space="preserve">
<value>Parameter "subscriptionId" is not allowed in the operations section, define it in the global parameters section instead</value>
</data>
<data name="ServiceDefinitionParametersMissingMessage" xml:space="preserve">
<value>Parameter "{0}" is referenced but not defined in the global parameters section of Service Definition</value>
</data>
<data name="UniqueResourcePaths" xml:space="preserve">
<value>Multiple resource providers are not allowed in a single spec. More than one the resource paths were found: '{0}'.</value>
</data>
<data name="GuidUsageNotRecommended" xml:space="preserve">
<value>Guid used in model definition '{1}' for property '{0}'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board.</value>
</data>
<data name="GetOperationNameNotValid" xml:space="preserve">
<value>'GET' operation '{0}' should use method name 'Get' or Method name start with 'List'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.</value>
</data>
<data name="InvalidMutabilityValueForReadOnly" xml:space="preserve">
<value>When property is modeled as "readOnly": true then x-ms-mutability extension can only have "read" value. When property is modeled as "readOnly": false then applying x-ms-mutability extension with only "read" value is not allowed. Extension contains invalid values: '{0}'.</value>
</data>
<data name="BooleanPropertyNotRecommended" xml:space="preserve">
<value>Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: {0}</value>
</data>
<data name="AllowedTopLevelProperties" xml:space="preserve">
<value>Top level properties should be one of name, type, id, location, properties, tags, plan, sku, etag, managedBy, identity, zones. Model definition '{0}' has extra properties ['{1}'].</value>
</data>
<data name="TrackedResourceGetOperationMissing" xml:space="preserve">
<value>Tracked resource '{0}' must have a get operation.</value>
</data>
<data name="DeleteOperationNameNotValid" xml:space="preserve">
<value>'DELETE' operation '{0}' should use method name 'Delete'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.</value>
</data>
<data name="PatchOperationNameNotValid" xml:space="preserve">
<value>'PATCH' operation '{0}' should use method name 'Update'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.</value>
</data>
<data name="PutOperationNameNotValid" xml:space="preserve">
<value>'PUT' operation '{0}' should use method name 'Create'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.</value>
</data>
<data name="CollectionObjectPropertiesNamingMessage" xml:space="preserve">
<value>Collection object '{0}' returned by list operation '{1}' with 'x-ms-pageable' extension, has no property named 'value'.</value>
</data>
<data name="TrackedResourcePatchOperationMissing" xml:space="preserve">
<value>Tracked resource '{0}' must have patch operation that at least supports the update of tags. It's strongly recommended that the PATCH operation supports update of all mutable properties as well.</value>
</data>
<data name="BodyPropertyNameCamelCase" xml:space="preserve">
<value>Property named: '{0}', must follow camelCase style. Example: '{1}'.</value>
</data>
<data name="DefinitionsPropertiesNameCamelCase" xml:space="preserve">
<value>Property named: '{0}', for definition: '{1}' must follow camelCase style. Example: '{2}'.</value>
</data>
<data name="ArmPropertiesBagValidationMessage" xml:space="preserve">
<value>Top level property names should not be repeated inside the properties bag for ARM resource '{0}'. Properties [{1}] conflict with ARM top level properties. Please rename these.</value>
</data>
<data name="ListOperationsNamingWarningMessage" xml:space="preserve">
<value>Since operation '{0}' response has model definition '{1}', it should be of the form "*_list*". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.</value>
</data>
<data name="LongRunningResponseNotValid" xml:space="preserve">
<value>A '{0}' operation '{1}' with x-ms-long-running-operation extension must have a valid terminal success status code {2}.</value>
</data>
<data name="PutOperationResourceResponseValidationMessage" xml:space="preserve">
<value>The 200 response model for an ARM PUT operation must have x-ms-azure-resource extension set to true in its hierarchy. Operation: '{0}' Model: '{1}'.</value>
</data>
<data name="ParametersPropertiesValidation" xml:space="preserve">
<value>Parameter Must have the "name" property defined with non-empty string as its value</value>
</data>
<data name="OperationIdNounConflictingModelNamesMessage" xml:space="preserve">
<value>OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to '{0}Model'. Consider using the plural form of '{1}' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.</value>
</data>
<data name="PutOperationRequestResponseSchemaMessage" xml:space="preserve">
<value>A PUT operation request body schema should be the same as its 200 response schema, to allow reusing the same entity between GET and PUT. If the schema of the PUT request body is a superset of the GET response body, make sure you have a PATCH operation to make the resource updatable. Operation: '{0}' Request Model: '{1}' Response Model: '{2}'</value>
</data>
<data name="SummaryDescriptionVaidationError" xml:space="preserve">
<value>The summary and description values should not be same.</value>
</data>
<data name="DeleteMustNotHaveRequestBody" xml:space="preserve">
<value>'Delete' operation '{0}' must not have a request body.</value>
</data>
<data name="SkuModelIsNotValid" xml:space="preserve">
<value>Sku Model definition '{0}' is not valid. A Sku model must have 'name' property. It can also have 'tier', 'size', 'family', 'capacity' as optional properties.</value>
</data>
<data name="PutGetPatchResponseInvalid" xml:space="preserve">
<value>{0} has different responses for PUT/GET/PATCH operations. The PUT/GET/PATCH operations must have same schema response.</value>
</data>
<data name="OperationsAPINotImplemented" xml:space="preserve">
<value>Operations API must be implemented for '{0}'.</value>
</data>
<data name="TrackedResourceListByImmediateParentOperationMissing" xml:space="preserve">
<value>The child tracked resource, '{0}' with immediate parent '{1}', must have a list by immediate parent operation.</value>
</data>
<data name="XMSPagableListByRGAndSubscriptionsMismatch" xml:space="preserve">
<value>For the tracked resource '{0}', the x-ms-pageable extension values must be same for list by resource group and subscriptions operations.</value>
</data>
<data name="TrackedResourceListByResourceGroupOperationMissing" xml:space="preserve">
<value>The tracked resource, '{0}', must have a list by resource group operation.(This rule does not apply for tenant level resources.)</value>
</data>
<data name="TrackedResourceListBySubscriptionsOperationMissing" xml:space="preserve">
<value>The tracked resource, '{0}', must have a list by subscriptions operation.</value>
</data>
<data name="GeneratingClient" xml:space="preserve">
<value>Generating client model from swagger model.</value>
</data>
<data name="ModelerInitialized" xml:space="preserve">
<value>Successfully initialized modeler {0} v {1}.</value>
</data>
<data name="IncompatibleTypesInBaseSchema" xml:space="preserve">
<value>Found incompatible property types {1}, {2} for property '{0}' in schema inheritance chain {3}</value>
</data>
<data name="IncompatibleTypesInSchemaComposition" xml:space="preserve">
<value>Found incompatible property types {1}, {2} for property '{0}' in schema {3}</value>
</data>
<data name="InfoSectionMissing" xml:space="preserve">
<value>Swagger specification is missing info section</value>
</data>
<data name="InputRequired" xml:space="preserve">
<value>Input parameter is required.</value>
</data>
<data name="InvalidAncestors" xml:space="preserve">
<value>The schema's '{0}' ancestors should have at lease one property</value>
</data>
<data name="InvalidCollectionFormat" xml:space="preserve">
<value>Collection format '{0}' is not a valid collection format (in parameter '{1}').</value>
</data>
<data name="InvalidTypeExtendsWithAllOf" xml:space="preserve">
<value>Cannot use 'extend' property with 'allOf' property in schema {0}</value>
</data>
<data name="InvalidTypeInSwaggerSchema" xml:space="preserve">
<value>'{0}' is not implemented in SwaggerSchema.ToType extension method.</value>
</data>
<data name="MultiCollectionFormatNotSupported" xml:space="preserve">
<value>Collection format "multi" is only supported for Query parameters (parameter '{0}').</value>
</data>
<data name="NoProduceOperationWithBody" xml:space="preserve">
<value>Method '{0}' does not declare any MIME type for the return body. Generated code will not deserialize the content.</value>
</data>
<data name="OptionsNotSupported" xml:space="preserve">
<value>Options HTTP verb is not supported.</value>
</data>
<data name="ParsingSwagger" xml:space="preserve">
<value>Parsing swagger json file.</value>
</data>
<data name="ReadOnlyNotRequired" xml:space="preserve">
<value>Property '{0}' in Model '{1}' is marked readOnly and is also required. This is not allowed.</value>
</data>
<data name="ReferenceDoesNotExist" xml:space="preserve">
<value>Reference path '{0}' does not exist in the definition section of the Swagger document.</value>
</data>
<data name="TitleMissing" xml:space="preserve">
<value>Swagger specification is missing title in info section</value>
</data>
<data name="UnknownSwaggerVersion" xml:space="preserve">
<value>Invalid swagger 2.0 specification. Missing version property. </value>
</data>
<data name="UnsupportedMimeTypeForResponseBody" xml:space="preserve">
<value>The operation '{0}' has a response body in response '{1}', but did not have a supported MIME type ('application/json' or 'application/octet-stream') in its Produces property.</value>
</data>
<data name="LongRunningOperationsWithLongRunningExtension" xml:space="preserve">
<value>The operation '{0}' returns 202 status code, which indicates a long running operation, please enable "x-ms-long-running-operation.</value>
</data>
<data name="XmsParameterLocation" xml:space="preserve">
<value>The parameter '{0}' is defined in global parameters section without 'x-ms-parameter-location' extension. This would add the parameter as the client property. Please ensure that this is exactly you want. If so, apply the extension "x-ms-parameter-location": "client". Else, apply the extension "x-ms-parameter-location": "method".</value>
</data>
<data name="LongRunningOperationsOptionsValidatorMessage" xml:space="preserve">
<value>A LRO Post operation with return schema must have "x-ms-long-running-operation-options" extension enabled.</value>
</data>
</root>