-
Notifications
You must be signed in to change notification settings - Fork 1.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
[ServiceBus] Fix linter errors and enable linting #18670
Conversation
sdk/servicebus/service-bus/test/public/amqpAnnotatedMessage.spec.ts
Outdated
Show resolved
Hide resolved
/azp run js - service-bus - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
@@ -2638,12 +2638,17 @@ versionsToTest(serviceApiVersions, {}, (serviceVersion, {}) => { | |||
"TestError: Topic path AND subscription path must be passed when invoking tests on rules" | |||
); | |||
} | |||
if (!ruleOptions?.filter || !ruleOptions.action) { | |||
throw new Error( | |||
"TestError: ruleOptions.filter and ruleOptions.action should have been set" |
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.
Now the live tests actually failed because ruleOptions
is undefined
. Before this PR we just force-passing undefined
for filter and action to atomClient.createRule()
. I also see a discrepancy that while createRule
doesn't allow undefined
values, they are allowed in putResource
(as CreateRuleOptions
):
azure-sdk-for-js/sdk/servicebus/service-bus/src/serviceBusAtomManagementClient.ts
Line 2198 in 16b6147
| CreateRuleOptions, |
Any insights? @HarshaNalluru @ramya-rao-a
Another option is to ignore the linting error if this is indeed expected.
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.
There is no point in creating a rule without a filter, right?
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.
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.
There is no point in creating a rule without a filter, right?
Then I don't know why the test would pass undefined
filter to createRule()
. We do create a always true sql filter internally
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.
Hmmm, we can remove the test
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.
ruleOptions?: Omit<Required<CreateSubscriptionOptions>["defaultRuleOptions"], "name">, |
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.
hmm, filter
is actually required now because of Required<>
. undefined is passed because ruleOptions
is undefined.
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.
So how do you want to move forward?
- filter will be required
- action is optional
- check for the existence of filter and throw if it is not provided to avoid
!
at the end? - check for the presence of action and call the overloads accordingly?
- update/remove the tests as needed(such as the "undefined" rule options one)?
- add tests if you feel a code path is missing?
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.
The API we use look fine. I had added throw will update it to only check filter. Don't need to do anything for action since it's optional, right? I will remove the test scenario of undefined ruleOptions as it doesn't apply for createRule()
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.
yes, you are right: calling different overloads based on action value
/azp run js - service-bus - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run js - service-bus - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
AssertionError: expecting valid error.message but error is [object CloseEvent]: expected undefined to be truthy
/azp run js - service-bus - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
Web ant97 2022 03 01 (Azure#19430) * Adds base for updating Microsoft.Web from version stable/2021-03-01 to version 2022-03-01 * Updates readme * Updates API version in new specs and examples * Carry fwd Microsoft.CertificateRegistration and Microsoft.DomainRegis… (Azure#18460) * Carry fwd Microsoft.CertificateRegistration and Microsoft.DomainRegistration RPs to Api-version 2022-03-01 * Add x-ms-enum for array of inline enums. Fix reference to older api version for common defs * Add examples for App Service Certificate orders * Add suppressions back * Add examples for Microsoft.DomainRegistration RP * Fixes from prettier * Remove unused example * Add Unhealthy CustomDomainStatus for StaticSites (Azure#18557) * Adding VnetRouteAllEnabled, VnetImagePullEnabled, VnetContentShareEnabled site properties to CommonDefinitions (Azure#18627) * Added vnet realted site properties to common definitions * removed tab Co-authored-by: Tanay Bhartia <[email protected]> * Add Ftp/Remote debug properties to Ase network config (Azure#18549) * Add Ftp/Remote debug properties to Ase network config * Switched changes to the right file * Add Networking config to hosting environment creates * Added some of the missing examples * Remove disallowed properties from example Ase GET response * Adjusted responses from other gets * Added a bunch more examples * Added other missing examples for Ase. * Added more missing examples for Ase. * fixed formatting * Edit some examples, add back privatelink apis and try to supress the errors for missing examples. * Fix suppress spelling and fix prettier * Added missing privatelink examples since suppressing did not work * Add Bring your own Backend operations (Azure#18517) * add bring your own backend operations * add missing files * fix json formattin * validation fixes * fix * fix more validation * fix ids * fix model validation * fix descriptions * fix environmentName description * change to 202 * revert change to 202 * customhostnamesites optional param for 2022 API version (Azure#18670) * fix DUPLICATE_PARAMETER * prettier * fix OBJECT_ADDITIONAL_PROPERTIES * fix random sub in examples * add optional hostname param to customHostnameSites RT and add examples * move changes from 2021 api version to 2022 * move examples to 2022 * Revert "add optional hostname param to customHostnameSites RT and add examples" This reverts commit 7fc318e190de2108222dbb869d9a6219a02cae2f. * remove examples from 2021 * fix lintDiff * prettier fix * model validation fix * suppress model validation in readme Co-authored-by: Elle Tojaroon <[email protected]> * [Microsoft.Web] Add CustomDnsSuffixConfiguration to ASE (Azure#18553) * [Microsoft.Web] Add CustomDnsSuffixConfiguration to AppServiceEnvironments * Add examples * Fix style issues * Add customdnssuffix to custom-words * Add CustomDnsSuffixConfiguration to AppServiceEnvironment definition * Address remaining model validation errors * Adjusted networking configuration definitions * Addressed Arm review feedback Co-authored-by: Jarod Aerts <[email protected]> * Fork/web ant97 2022 03 01 (Azure#19259) * Added DeploymentStatus API specs and examples * change status to enum, rm extra dot * suppress missing examples for now * rm id from List Deployment Slot examples * rm location, and rename deploymentId in GetSiteDeploymentStatus examples * change model as string to true, add 202 operations for DeploymentStatus ops to spec * rename operationId to deploymentStatusId, undo deploymentId rename * add long running op, as per linter Co-authored-by: Shubham Dhond <[email protected]> Co-authored-by: Weidong Xu <[email protected]> * PublicNetworkAccess Swagger Change (Azure#19352) * add publicNetworkAccess property in site for swagger * add suppression to fix Model Validation CI * Add allowed values in the description * Add specs for Hosting Environment Maintenance Control (Azure#18691) * Add documentation for Hosting Environment Maintenance Control * Update example file name * Make UpgradePreference non-nullable * Correct indentation to 2 spaces * Fix upgradePreference indentation * Address swagger feedback. Add enums with descriptions. * Move testNotification to request body. Update description text * Fix testNotification * Fix example * Replace TestNotification parameter with TestUpgradeNotification API * Rename to TestUpgradeAvailableNotification * Added logic apps operations (Azure#18604) * Added Initial Operations and some definitions * Adding additional objects to support Logic Apps operations * Updated path and parameters to match testing * Prettier Fixes * oav validat-example fixes * Github validation fixes * Prettier * Updated examples and paths * Prettier * Revert "Prettier" This reverts commit da090adf8005e0bd6fdc2ddebbd4390e5c4b6b20. * Prettier * Fixed model validation errors * Filled in nextLinkName values * Fixing swagger lintdiff errors * added x-ms-long-running to async calls * Adds numberOfWorkers to app service plan (Azure#19475) * Adds numberOfWorkers to app service plan * Add suppression for missing ASP examples * Updating to fix workflow errors (Azure#19490) * Removed conflicting resource definition and added reference to CommonDefinitions.json (Azure#19507) * Removed conflicting resource definition and added reference to CommonDefinitions.json * Updated resource to have workflow version * Updated nextLink object to be correctly tagged (Azure#19560) * Updated nextLink object to be correctly tagged * Adding value placeholder * Updated SKU to remove conflict * Updated x-ms-enum * Added missing model * Adding more missing models * Add suppressions for missing examples (Azure#19563) Co-authored-by: Joseph Lin <[email protected]> Co-authored-by: Tanay Bhartia <[email protected]> Co-authored-by: Tanay Bhartia <[email protected]> Co-authored-by: JarodAertsMs <[email protected]> Co-authored-by: annikel <[email protected]> Co-authored-by: Paviya (Elle) Tojaroon <[email protected]> Co-authored-by: Elle Tojaroon <[email protected]> Co-authored-by: Chris Chen <[email protected]> Co-authored-by: Jarod Aerts <[email protected]> Co-authored-by: edwin-msft <[email protected]> Co-authored-by: Shubham Dhond <[email protected]> Co-authored-by: Weidong Xu <[email protected]> Co-authored-by: jiansong-msft <[email protected]> Co-authored-by: Derek Johnson <[email protected]> Co-authored-by: Alex Karcher <[email protected]>
Some reports are ignored
Function
object
/any
used in deserialization{}
in public apiwithResponse<{}>