Skip to content
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

Merged
2 commits merged into from
Feb 11, 2021

Conversation

ramya-rao-a
Copy link
Contributor

@ramya-rao-a ramya-rao-a commented Feb 11, 2021

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!

@@ -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".
Copy link
Contributor Author

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?

image

Copy link
Member

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 {}.

Copy link
Contributor Author

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

@ghost
Copy link

ghost commented Feb 11, 2021

Hello @ramya-rao-a!

Because this pull request has the auto-merge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

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 (@msftbot) and give me an instruction to get started! Learn more here.

@ghost ghost merged commit 753b891 into Azure:master Feb 11, 2021
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants