[Communication][Chat] Promote file attachment type from Beta -> GA #27395
openapi-pipeline-app / ~[NotRequired_Staging] Swagger LintDiff
succeeded
Jan 30, 2024 in 4m 27s
~[NotRequired_Staging] Swagger LintDiff succeeded
ppe/LintDiff
View Azure DevOps build log for more details.
Details
| compared tags (via openapi-validator vbeta) | new version | base version |
|---|---|---|
| package-chat-2024-03-07 | package-chat-2024-03-07(45984f1) | default(main) |
The following errors/warnings exist before current PR submission:
Only 50 items are listed, please refer to log for more details.
| Rule | Message |
|---|---|
|
The host parameter must be typed 'type 'string', format 'url''. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L1782 |
|
Per the Noun_Verb convention for Operation Ids, the noun 'Chat' 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. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L1069 |
|
Per the Noun_Verb convention for Operation Ids, the noun 'ChatThread' 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. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L1006 |
|
Per the Noun_Verb convention for Operation Ids, the noun 'ChatThread' 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. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L934 |
|
Per the Noun_Verb convention for Operation Ids, the noun 'Chat' 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. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L858 |
|
Per the Noun_Verb convention for Operation Ids, the noun 'Chat' 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. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L781 |
| Error response should contain a x-ms-error-code header. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L1183 |
|
| Error response should contain a x-ms-error-code header. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L1176 |
|
| Error response should contain a x-ms-error-code header. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L1169 |
|
| Error response should contain a x-ms-error-code header. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L1162 |
|
| All success responses except 202 & 204 should define a response body. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L1159 |
|
| Operation is missing a default response. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L1158 |
|
| The body parameter is not marked as required. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L1149 |
|
| Path parameter should specify a maximum length (maxLength) and characters allowed (pattern). Location: Chat/stable/2024-03-07/communicationserviceschat.json#L1139 |
|
| Error response should contain a x-ms-error-code header. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L1110 |
|
| Error response should contain a x-ms-error-code header. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L1103 |
|
| Error response should contain a x-ms-error-code header. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L1096 |
|
| Error response should contain a x-ms-error-code header. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L1089 |
|
| Operation is missing a default response. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L1085 |
|
| Path parameter should specify a maximum length (maxLength) and characters allowed (pattern). Location: Chat/stable/2024-03-07/communicationserviceschat.json#L1074 |
|
| Error response should contain a x-ms-error-code header. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L1050 |
|
| Error response should contain a x-ms-error-code header. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L1043 |
|
| Error response should contain a x-ms-error-code header. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L1036 |
|
| Error response should contain a x-ms-error-code header. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L1029 |
|
| Operation is missing a default response. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L1022 |
|
| Path parameter should specify a maximum length (maxLength) and characters allowed (pattern). Location: Chat/stable/2024-03-07/communicationserviceschat.json#L1011 |
|
| Error response should contain a x-ms-error-code header. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L987 |
|
| Error response should contain a x-ms-error-code header. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L980 |
|
| Error response should contain a x-ms-error-code header. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L973 |
|
| Error response should contain a x-ms-error-code header. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L966 |
|
| Operation is missing a default response. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L962 |
|
| Path parameter should specify a maximum length (maxLength) and characters allowed (pattern). Location: Chat/stable/2024-03-07/communicationserviceschat.json#L942 |
|
| Error response should contain a x-ms-error-code header. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L909 |
|
| Error response should contain a x-ms-error-code header. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L902 |
|
| Error response should contain a x-ms-error-code header. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L895 |
|
| Error response should contain a x-ms-error-code header. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L888 |
|
| Operation is missing a default response. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L881 |
|
| Error response should contain a x-ms-error-code header. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L836 |
|
| Error response should contain a x-ms-error-code header. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L829 |
|
| Error response should contain a x-ms-error-code header. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L822 |
|
| Error response should contain a x-ms-error-code header. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L815 |
|
| Using post for a create operation is discouraged. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L809 |
|
| Operation is missing a default response. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L808 |
|
| Operation might be pageable. Consider adding the x-ms-pageable extension. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L776 |
|
| Error response should contain a x-ms-error-code header. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L760 |
|
| Error response should contain a x-ms-error-code header. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L753 |
|
| Error response should contain a x-ms-error-code header. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L746 |
|
| Error response should contain a x-ms-error-code header. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L739 |
|
| Using post for a create operation is discouraged. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L733 |
|
| Operation is missing a default response. Location: Chat/stable/2024-03-07/communicationserviceschat.json#L732 |
Loading