-
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
[Service Bus] subQueue -> subQueueType #12223
Conversation
/azp run js - servicebus - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
Should we do the same for ReceiveMode i.e. inline it instead of having a dedicated type? |
Having an alias(or dedicated type) helps in reusing it wherever we declare the |
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.
This is great. Having the literals inline is awesome.
syncing changes from 2020-06-01-preview api (Azure#12462) * [2020-06-01-preview] Update namedvalue add refreshSecret operation (Azure#12223) * add refreshSecret * addressing comments * add 202 * address comments * parenthesis Co-authored-by: Kacie Kang <jikang@microsoft.com> * [2020-06-01-preview] Update certificate add refreshSecret operation (Azure#12226) * add refresh * add path * add keyvault part * address comments Co-authored-by: Kacie Kang <jikang@microsoft.com> Co-authored-by: Kacie Kang <jikang@microsoft.com>
Unlike other languages, we don not use enums and use string literals instead. For the
subQueue
property, this opens up a potential confusion for people if they think they can pass in queue names. To help with this, in this PR wesubQueue
tosubQueueType