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
@@ -113,7 +113,7 @@ Various APIViews are generated as part of the Azure REST API specs PR build. Amo
113
113
### If an expected APIView was not generated, follow the step below to troubleshoot.
114
114
115
115
- On the CI check click on `details` > `View Azure DevOps build log for more details` to view the devOps logs.
116
-
- Investigate the CI job for the languge with error. TypeSpec and Swagger APIViews are generated as part of the `AzureRestApiSpecsPipeline` stage in the `TypeSpecAPIView` and `SwaggerAPIView` jobs respectively, while APIViews for other SDK languges are generated in their respective language jobs in the `SDK Automation` stage.
116
+
- Investigate the CI job for the language with error. TypeSpec and Swagger APIViews are generated as part of the `AzureRestApiSpecsPipeline` stage in the `TypeSpecAPIView` and `SwaggerAPIView` jobs respectively, while APIViews for other SDK languages are generated in their respective language jobs in the `SDK Automation` stage.
117
117
- Ensure that all previous checks in the job are green before proceeding.
118
118
119
119
### Diagnosing APIView failure for SDK Language (not Swagger or TypeSpec)
@@ -247,35 +247,34 @@ oav validate-spec <openapi-spec-path>
247
247
Please see [readme](https://github.com/Azure/oav/blob/bd04e228b4181c53769ed88e561dec5212e77253/README.md) for how to install or run tool in details.
248
248
Refer to [Semantic and Model Violations Reference](https://github.com/Azure/azure-rest-api-specs/blob/main/documentation/Semantic-and-Model-Violations-Reference.md) for detailed description of validations and how-to-fix guidance.
249
249
250
-
## `Swagger SpellCheck`
251
-
252
-
If you receive a spelling failure either fix the spelling to match or if there are words that need to be suppressed for your service then add the word to the override list in [cspell.json](https://github.com/Azure/azure-rest-api-specs/blob/main/cSpell.json). Either
253
-
add to your existing section or create a new section for your specific spec or service family if the work is more generally used in lots of files under your service.
If you receive a spelling failure either fix the spelling in source. If there are words that need to be suppressed for
253
+
your service, add the word to the override list in the `words` list in the `specification/<service>/cspell.json`
254
+
file for your service.
255
+
256
+
If the `specification/<service>/cspell.json` file does not exist, create it using the example below and set the `words`
257
+
list to the words that need to be suppressed. Both `version` and `import` fields are required, use the values in the
258
+
example.
259
+
260
+
For example (note the words list is sorted alphabetically):
261
+
262
+
```json
263
+
{
264
+
"version": "0.2",
265
+
"import": [
266
+
"../../cspell.json"
267
+
],
268
+
"words": [
269
+
"aardvark",
270
+
"zoology"
271
+
]
272
+
}
272
273
```
273
274
274
-
Words are case-insensitive so use lower case for the word list.
275
+
Words are case-insensitive so you only need to add the word once.
275
276
276
-
If you need more information on see [cspell configuration](https://cspell.org/configuration/).
277
-
278
-
*Note*: We are trying to move away from one shared dictionary file so try and avoid editing custom-words.txt in the root as it will likely go away in the future.
277
+
For more information see [cspell configuration](https://cspell.org/configuration/).
279
278
280
279
## `TypeSpec Validation`
281
280
@@ -313,4 +312,4 @@ Following checks have been removed from the validation toolchain as of August 20
313
312
[APIView Support Teams Channel]: https://teams.microsoft.com/l/channel/19%3A3adeba4aa1164f1c889e148b1b3e3ddd%40thread.skype/APIView?groupId=3e17dcb0-4257-4a30-b843-77f47f1d4121&tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47
[Azure REST API specs PR]: https://eng.ms/docs/products/azure-developer-experience/design/api-specs-pr/api-specs-pr
316
-
[TypeSpec Discussions Teams channel]: https://teams.microsoft.com/l/channel/19%3A906c1efbbec54dc8949ac736633e6bdf%40thread.skype/TypeSpec%20Discussion%20%F0%9F%90%AE?groupId=3e17dcb0-4257-4a30-b843-77f47f1d4121&tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47
315
+
[TypeSpec Discussions Teams channel]: https://teams.microsoft.com/l/channel/19%3A906c1efbbec54dc8949ac736633e6bdf%40thread.skype/TypeSpec%20Discussion%20%F0%9F%90%AE?groupId=3e17dcb0-4257-4a30-b843-77f47f1d4121&tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47
0 commit comments