Skip to content

Commit

Permalink
typo: Microsoft.DataFactory (#4675)
Browse files Browse the repository at this point in the history
- azure-mgmt-dafactory -> azure-mgmt-datafactory
- arbitary -> arbitrary
- requries -> requires
- Fitler -> Filter
  • Loading branch information
nschonni authored and sergey-shandar committed Dec 4, 2018
1 parent 72e2943 commit 0a159a0
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -2819,7 +2819,7 @@
]
},
"FilterActivityTypeProperties": {
"description": "Fitler activity properties.",
"description": "Filter activity properties.",
"properties": {
"items": {
"description": "Input array on which filter should be applied.",
Expand Down
6 changes: 3 additions & 3 deletions specification/datafactory/resource-manager/readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -94,7 +94,7 @@ python:
license-header: MICROSOFT_MIT_NO_VERSION
payload-flattening-threshold: 2
namespace: azure.mgmt.datafactory
package-name: azure-mgmt-dafactory
package-name: azure-mgmt-datafactory
package-version: 1.0.0
clear-output-folder: true
```
Expand Down Expand Up @@ -188,7 +188,7 @@ directive:
from: datafactory.json
reason:
- Flattening does not work well with polymorphic models.
- TriggerResource.properties is an arbitary dictionary and cannot be flattened.
- TriggerResource.properties is an arbitrary dictionary and cannot be flattened.
- suppress: R2018 # XmsEnumValidation
where:
- $.definitions.Expression.properties.type
Expand Down Expand Up @@ -256,7 +256,7 @@ directive:
- $.definitions.SelfHostedIntegrationRuntimeNode.properties.isActiveDispatcher
- $.definitions.IntegrationRuntimeConnectionInfo.properties.isIdentityCertExprired
reason:
- toBeExportedForShoebox is property we send to Azure Monitor which requries the boolean type
- toBeExportedForShoebox is property we send to Azure Monitor which requires the boolean type
- The other properties are simple and self explanatory
```

0 comments on commit 0a159a0

Please sign in to comment.