@@ -149,8 +149,7 @@ If the resource is a singleton resource, the last noun may be the plural form of
149149##### Implementation details
150150Rule checks for the following conditions:
151151 - Applies only to GET methods on single resources or singleton resources
152- - Generates the expected OperationId given the resource identifier
153- - Confirms that the existing operationId is compliant with generated IPA Compliant OperationId
152+ - Confirms that the existing OperationId is compliant with generated IPA Compliant OperationId
154153
155154
156155
@@ -216,8 +215,7 @@ The noun(s) in the Operation ID should be the collection identifiers from the re
216215Rule checks for the following conditions:
217216 - Applies only to GET methods on resource collection paths
218217 - Ignores singleton resources
219- - Generates the expected OperationId given the resource identifier
220- - Confirms that the existing operationId is compliant with generated IPA Compliant OperationId
218+ - Confirms that the existing OperationId is compliant with generated IPA Compliant OperationId
221219
222220
223221
@@ -308,8 +306,7 @@ The noun(s) in the Operation ID should be the collection identifiers from the re
308306##### Implementation details
309307Rule checks for the following conditions:
310308 - Applies only to POST methods on resource collection paths
311- - Generates the expected OperationId given the resource identifier
312- - Confirms that the existing operationId is compliant with generated IPA Compliant OperationId
309+ - Confirms that the existing OperationId is compliant with generated IPA Compliant OperationId
313310
314311
315312
@@ -392,8 +389,7 @@ If the resource is a singleton resource, the last noun may be the plural form of
392389##### Implementation details
393390Rule checks for the following conditions:
394391 - Validation checks the PATCH/PUT methods for single resource paths and [ singleton resources] ( https://go/ipa/113 ) .
395- - Generates the expected OperationId given the resource identifier
396- - Confirms that the existing operationId is compliant with generated IPA Compliant OperationId
392+ - Confirms that the existing OperationId is compliant with generated IPA Compliant OperationId
397393
398394
399395
@@ -448,8 +444,7 @@ The noun(s) in the Operation ID should be the collection identifiers from the re
448444##### Implementation details
449445Rule checks for the following conditions:
450446 - Applies to all DELETE methods for single resource endpoints (with path parameters)
451- - Generates the expected OperationId given the resource identifier
452- - Confirms that the existing operationId is compliant with generated IPA Compliant OperationId
447+ - Confirms that the existing OperationId is compliant with generated IPA Compliant OperationId
453448
454449
455450
@@ -509,8 +504,7 @@ The noun(s) in the Operation ID should be the collection identifiers from the re
509504##### Implementation details
510505Rule checks for the following conditions:
511506 - Applies only to paths containing custom method identifiers (with colon format)
512- - Generates the expected OperationId given the resource identifier and the method name portion following the colon
513- - Confirms that the existing operationId is compliant with generated IPA Compliant OperationId
507+ - Confirms that the existing OperationId is compliant with generated IPA Compliant OperationId
514508
515509
516510
0 commit comments