-
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
[Event Hubs] Fix remaining TSDoc linting errors #13746
Conversation
@@ -9,8 +9,8 @@ import { parseConnectionString } from "@azure/core-amqp"; | |||
export interface EventHubConnectionStringProperties { | |||
/** | |||
* The fully qualified Event Hub namespace extracted from the "Endpoint" in the | |||
* connection string. This is likely to be similar to "{yournamespace}.servicebus.windows.net". | |||
* This is typically used to construct the EventHub{Producer|Consumer}Client. | |||
* connection string. This is likely to be similar to "\{yournamespace\}.servicebus.windows.net". |
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.
@deyaaeldeen Is this the recommended way to get past the error from tsdoc linter on malformed tags?
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 do not remember if I have seen this before but I think if you enclose it in `` instead of "" the error will go away. If not, perhaps try <> instead of {}.
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.
Ah, backtick works! Updated in e97da9e
Hello @ramya-rao-a! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
This PR fixes the remaining TSDoc related linting errors in Event Hubs, thereby reducing the number of total linter problems from 70 to 38. Related to #12953 and #10777
@chradek Of the 38, errors are 18 and warnings are 20. Handing over the rest to your capable hands!