-
Notifications
You must be signed in to change notification settings - Fork 51
Updated the rule so it doesn't error on enums or public properties #824
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -180,7 +180,8 @@ const ruleset: any = { | |
| // RPC Code: RPC-Async-V1-11, RPC-Async-V1-14 | ||
| PostResponseCodes: { | ||
| rpcGuidelineCode: "RPC-Async-V1-11, RPC-Async-V1-14, RPC-POST-V1-02, RPC-POST-V1-03", | ||
| description: "Synchronous POST must return 200 when a response body is required or 204 when no body is needed; LRO POST must initially return 202, with the final response returning 200 if a body is expected or 204 if not.", | ||
| description: | ||
| "Synchronous POST must return 200 when a response body is required or 204 when no body is needed; LRO POST must initially return 202, with the final response returning 200 if a body is expected or 204 if not.", | ||
| severity: "error", | ||
| disableForTypeSpecDataPlane: true, | ||
| disableForTypeSpecDataPlaneReason: | ||
|
|
@@ -690,7 +691,7 @@ const ruleset: any = { | |
| message: "{{error}}", | ||
| severity: "error", | ||
| resolved: true, | ||
| given: ["$[paths,'x-ms-paths'].*.[put,get,post].responses.*.schema.properties"], | ||
| given: ["$.definitions.*.properties"], | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Assuming this change is due to - check all the models irrespective of being used or not?
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. You're right, this ensures we don't miss any secret properties, similar to how the typespec team handled their changes. |
||
| then: { | ||
| function: XMSSecretInResponse, | ||
| }, | ||
|
|
||
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.
is this intended?
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.
Rush prep has adjusted the spaces, and this happens with every PR. I usually discard it, but I thought I would push it this time.