-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Update typespec for ApplicationInsights LiveMetrics #28320
base: main
Are you sure you want to change the base?
Conversation
Next Steps to Merge✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge. |
Swagger Validation Report
|
Compared specs (v0.10.8) | new version | base version |
---|---|---|
livemetrics.json | 2024-04-01-preview(5e0da64) | 2024-04-01-preview(main) |
Rule | Message |
---|---|
1023 - TypeFormatChanged |
The new version has a different format '' than the previous one 'uri'. New: LiveMetrics/preview/2024-04-01-preview/livemetrics.json#L892:9 Old: LiveMetrics/preview/2024-04-01-preview/livemetrics.json#L893:9 |
1025 - RequiredStatusChange |
The 'required' status changed from the old version('True') to the new version('False'). New: LiveMetrics/preview/2024-04-01-preview/livemetrics.json#L59:9 Old: LiveMetrics/preview/2024-04-01-preview/livemetrics.json#L59:9 |
1025 - RequiredStatusChange |
The 'required' status changed from the old version('True') to the new version('False'). New: LiveMetrics/preview/2024-04-01-preview/livemetrics.json#L618:7 Old: LiveMetrics/preview/2024-04-01-preview/livemetrics.json#L618:7 |
️️✔️
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 |
---|---|---|
2024-04-01-preview | 2024-04-01-preview(5e0da64) | 2024-04-01-preview(main) |
The following errors/warnings exist before current PR submission:
Rule | Message |
---|---|
Security definition should have a description. Location: LiveMetrics/preview/2024-04-01-preview/livemetrics.json#L44 |
|
OperationId should be of the form 'Noun_Verb' Location: LiveMetrics/preview/2024-04-01-preview/livemetrics.json#L57 |
|
The body parameter is not marked as required. Location: LiveMetrics/preview/2024-04-01-preview/livemetrics.json#L87 |
|
Error response should contain a x-ms-error-code header. Location: LiveMetrics/preview/2024-04-01-preview/livemetrics.json#L116 |
|
Error response schema should contain an object property named error .Location: LiveMetrics/preview/2024-04-01-preview/livemetrics.json#L118 |
|
OperationId should be of the form 'Noun_Verb' Location: LiveMetrics/preview/2024-04-01-preview/livemetrics.json#L132 |
|
The body parameter is not marked as required. Location: LiveMetrics/preview/2024-04-01-preview/livemetrics.json#L147 |
|
Error response should contain a x-ms-error-code header. Location: LiveMetrics/preview/2024-04-01-preview/livemetrics.json#L168 |
|
Error response schema should contain an object property named error .Location: LiveMetrics/preview/2024-04-01-preview/livemetrics.json#L170 |
|
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: LiveMetrics/preview/2024-04-01-preview/livemetrics.json#L696 |
|
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: LiveMetrics/preview/2024-04-01-preview/livemetrics.json#L700 |
️️✔️
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
|
/azp run |
Azure Pipelines successfully started running 4 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 4 pipeline(s). |
@@ -390,7 +390,7 @@ model KeyValuePairStringString { | |||
key: string; | |||
|
|||
@doc("Value of the key-value pair.") | |||
value: string; | |||
value?: string; |
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.
I don't understand this change. I saw your explanation in the PR description (BTW thank you for this -- I see many PRs that lack this kind of explanation):
This change makes the value property settable
But this should not be dependent on whether the property is required or optional. Making the value property optional means that a key-value-pair that only contains a key is valid -- which makes no sense to me.
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.
Discussed with my team, we'll remove this change.
changing this PR to Draft.
|
This PR is a follow up to #27430
Data Plane API - Pull Request
Trying to onboard my .NET SDK to the new typespec api. Azure/azure-sdk-for-net#42714
I found a few issues that needed to be changed:
tspconfig.yaml
to support .NET SDKmodels.tsp
This value is recorded after an application receives a request. The url is being recorded to store in telemetry. Using the Uri class here is adding unnecessary allocations and validations.
This change makes the value property settable, which is needed as part of implementing filtering.
npx tsp compile
linkAPI Info: The Basics
Most of the information about your service should be captured in the issue that serves as your API Spec engagement record.
Is this review for (select one):
Change Scope
This section will help us focus on the specific parts of your API that are new or have been modified.
Please share a link to the design document for the new APIs, a link to the previous API Spec document (if applicable), and the root paths that have been updated.
Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the
Generated ApiView
comment added to this PR. You can use ApiView to show API versions diff.Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.
❔Got questions? Need additional info?? We are here to help!
Contact us!
The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.
Click here for links to tools, specs, guidelines & other good stuff
Tooling
Guidelines & Specifications
Helpful Links
Checks stuck in `queued` state?
If the PR CI checks appear to be stuck in `queued` state, please add a comment with contents `/azp run`. This should result in a new comment denoting a `PR validation pipeline` has started and the checks should be updated after few minutes.