DataFactory: fix headers schema issue #28210
Merged
openapi-pipeline-app / Swagger LintDiff
succeeded
Mar 12, 2024 in 5m 2s
Swagger LintDiff succeeded
Details
| Compared specs (v2.2.0) | new version | base version |
|---|---|---|
| package-2018-06 | package-2018-06(120cce6) | package-2018-06(main) |
The following errors/warnings exist before current PR submission:
| Rule | Message |
|---|---|
|
Property name should be camel case. Location: stable/2018-06-01/entityTypes/Pipeline.json#L9095 |
|
Property name should be camel case. Location: stable/2018-06-01/entityTypes/Pipeline.json#L9116 |
| Consider using x-ms-client-flatten to provide a better end user experience Location: stable/2018-06-01/entityTypes/Pipeline.json#L68 |
|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: stable/2018-06-01/entityTypes/Pipeline.json#L273 |
|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: stable/2018-06-01/entityTypes/Pipeline.json#L277 |
|
| Schema should have a description or title. Location: stable/2018-06-01/entityTypes/Pipeline.json#L3214 |
|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: stable/2018-06-01/entityTypes/Pipeline.json#L6637 |
|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: stable/2018-06-01/entityTypes/Pipeline.json#L6924 |
|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: stable/2018-06-01/entityTypes/Pipeline.json#L6944 |
|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: stable/2018-06-01/entityTypes/Pipeline.json#L7183 |
|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: stable/2018-06-01/entityTypes/Pipeline.json#L7192 |
|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: stable/2018-06-01/entityTypes/Pipeline.json#L7419 |
|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: stable/2018-06-01/entityTypes/Pipeline.json#L8106 |
|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: stable/2018-06-01/entityTypes/Pipeline.json#L8116 |
|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: stable/2018-06-01/entityTypes/Pipeline.json#L8120 |
|
| Consider using x-ms-client-flatten to provide a better end user experience Location: stable/2018-06-01/entityTypes/Pipeline.json#L8362 |
|
| Consider using x-ms-client-flatten to provide a better end user experience Location: stable/2018-06-01/entityTypes/Pipeline.json#L8489 |
|
| Missing identifier id in array item property Location: stable/2018-06-01/entityTypes/Pipeline.json#L9240 |
Loading