-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Change two property types for route spec #28576
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change two property types for route spec #28576
Conversation
Next Steps to MergeImportant checks have failed. As of today they are not blocking this PR, but in near future they will.Addressing the following failures is highly recommended:
|
Swagger Validation Report
|
| Compared specs (v0.10.9) | new version | base version |
|---|---|---|
| route.json | 1.0(eb7a854) | 1.0(main) |
️️✔️Breaking Change(Cross-Version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️⚠️LintDiff: 0 Warnings warning [Detail]
| Compared specs (v2.2.2) | new version | base version |
|---|---|---|
| 1.0 | 1.0(eb7a854) | 1.0(main) |
The following errors/warnings exist before current PR submission:
Only 30 items are listed, please refer to log for more details.
| Rule | Message |
|---|---|
IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Route/preview/1.0/route.json#L525 |
IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Route/preview/1.0/route.json#L533 |
IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Route/preview/1.0/route.json#L541 |
IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Route/preview/1.0/route.json#L576 |
IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Route/preview/1.0/route.json#L766 |
OperationIdNounVerb |
Per the Noun_Verb convention for Operation Ids, the noun 'Route' 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: Route/preview/1.0/route.json#L891 |
OperationIdNounVerb |
Per the Noun_Verb convention for Operation Ids, the noun 'Route' 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: Route/preview/1.0/route.json#L997 |
OperationIdNounVerb |
Per the Noun_Verb convention for Operation Ids, the noun 'Route' 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: Route/preview/1.0/route.json#L1038 |
OperationIdNounVerb |
Per the Noun_Verb convention for Operation Ids, the noun 'Route' 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: Route/preview/1.0/route.json#L1146 |
IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Route/preview/1.0/route.json#L1165 |
IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Route/preview/1.0/route.json#L1176 |
IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Route/preview/1.0/route.json#L1188 |
OperationIdNounVerb |
Per the Noun_Verb convention for Operation Ids, the noun 'Route' 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: Route/preview/1.0/route.json#L1318 |
IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Route/preview/1.0/route.json#L1338 |
IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Route/preview/1.0/route.json#L1349 |
IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Route/preview/1.0/route.json#L1355 |
OperationIdNounVerb |
Per the Noun_Verb convention for Operation Ids, the noun 'Route' 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: Route/preview/1.0/route.json#L1502 |
OperationIdNounVerb |
Per the Noun_Verb convention for Operation Ids, the noun 'Route' 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: Route/preview/1.0/route.json#L1663 |
OperationIdNounVerb |
Per the Noun_Verb convention for Operation Ids, the noun 'Route' 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: Route/preview/1.0/route.json#L1712 |
OperationIdNounVerb |
Per the Noun_Verb convention for Operation Ids, the noun 'Route' 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: Route/preview/1.0/route.json#L1753 |
IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Route/preview/1.0/route.json#L1892 |
IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Route/preview/1.0/route.json#L1897 |
IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Route/preview/1.0/route.json#L1902 |
IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Route/preview/1.0/route.json#L1919 |
IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Route/preview/1.0/route.json#L1924 |
IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Route/preview/1.0/route.json#L1953 |
IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Route/preview/1.0/route.json#L1958 |
IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Route/preview/1.0/route.json#L1963 |
IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Route/preview/1.0/route.json#L1974 |
IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Route/preview/1.0/route.json#L1979 |
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️SwaggerAPIView succeeded [Detail] [Expand]
️️✔️TypeSpecAPIView succeeded [Detail] [Expand]
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️️✔️SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
️️✔️PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
️️✔️Automated merging requirements met succeeded [Detail] [Expand]
Swagger Generation Artifacts
|
Generated ApiView
|
|
Thank you for your contribution jecmenicanikola! We will review the pull request and get back to you soon. |
|
Hi @mikekistler and @bexxx , |
|
Also adding @FarazGIS as reviewer for awareness |
mikekistler
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. 👍
| "description": "Sections of the route that are located within urban areas." | ||
| } | ||
| ] | ||
| "description": "Specifies which of the section types is reported in the route response. <br><br>For example if sectionType = pedestrian the sections which are suited for pedestrians only are returned. Can be specified multiple times in one request, for example, '§ionType=carTrain§ionType=pedestrain§ionType=motorway'. The default sectionType refers to the travelMode input. By default travelMode is set to car", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo: pedestrain -> pedestrian
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dubiety done
While investigating Azure/azure-sdk-for-net#39869 and Azure/azure-sdk-for-net#38719, I found that the type returned by the server and the type that the server expects does not match what is currently on the spec.
This PR changes the type of 'sectionType' property from string to array and the type of 'roundaboutExitNumber' property from string to int.
When the SDK code is regenerated with these changes, custom code will have to be adapted to the new types.