Missing docs for azure-sb package
See original GitHub issueazure-sb
is the legacy package for Service Bus
Interestingly, it has code to support the Notification Hubs service as well, and therefore is not legacy on that front.
We plan to copy out the Notification Hubs code from this package to a separate package soon. But meanwhile, API reference docs for this package needs to show up under Notification Hubs for current users of azure-sb
If possible, reference docs for azure-sb
should show up under “Service Bus” but under the “Legacy” moniker.
cc @scbedd
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
"packages" resource documentation missing? #8757 - GitHub
Where is the documentation for package resources? It would appear the schema looks like this: packages: - package: type: connection: name: ...
Read more >GetDocumentOptions.SelectedFields Property (Azure.Search ...
Any field not retrieved will be missing from the returned document. If empty, all fields marked as retrievable in the schema are returned....
Read more >Work with Azure Functions Core Tools | Microsoft Learn
Learn how to code and test Azure Functions from the command prompt or terminal on your local computer before you run them on...
Read more >Indexer troubleshooting guidance - Azure Cognitive Search
Missing documents. Indexers extract documents or rows from an external data source and create search documents which are then indexed by the ...
Read more >How to install the Azure CLI - Microsoft Learn
Learn how to install and run the Azure CLI on macOS using the homebrew package manager. The Azure CLI has been tested on...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
On second thoughts…
Let’s go with 2) for now. The splitting of Notification Hubs code from azure-sb to a new package should happen sooner than later. So, you can skip 1)
I’ll log a separate request once the new package is out to get the ref docs generated for it under Notification Hubs
Thanks @scbedd!
I can see the docs at https://docs.microsoft.com/en-us/javascript/api/azure-sb/?view=azure-node-legacy