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

Fix F1 help link for error messages #46850

Merged
merged 17 commits into from
Oct 6, 2020
Merged

Fix F1 help link for error messages #46850

merged 17 commits into from
Oct 6, 2020

Conversation

Youssef1313
Copy link
Member

@Youssef1313 Youssef1313 commented Aug 15, 2020

Discussion started in dotnet/docs#20069 by @ChrisMaddock.

Fixes dotnet/docs#16448
Fixes #40863
Fixes #46829

Prefer squash/merge

@Youssef1313 Youssef1313 requested a review from a team as a code owner August 15, 2020 13:06
}

return string.Empty;
return $"https://msdn.microsoft.com/query/dev16.query?appId=Dev16IDEF1&l={CultureInfo.CurrentCulture}&k=k({GetId(code)});k(DevLang-csharp)&rd=true";
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't particularly like hardcoding dev16 into the compiler, I think any link would need to be VS-version agnostic.

What would happen when we add new error codes to the compiler that aren't yet doc'd?

Copy link
Member Author

@Youssef1313 Youssef1313 Aug 17, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@333fred

I don't particularly like hardcoding dev16 into the compiler, I think any link would need to be VS-version agnostic.

I don't think it's a big deal. I even don't know how it matters if it's dev16 or dev15 or whatever version. Both redirects to the correct page.

If the docs consolidated all error messages in the same directory, we can rely on it as a different link.

What would happen when we add new error codes to the compiler that aren't yet doc'd?

It will redirect to https://docs.microsoft.com/en-us/dotnet/csharp/misc/sorry-we-don-t-have-specifics-on-this-csharp-error

(Currently, it won't do that for all error messages. That will get fixed by dotnet/docs#20069

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think this needs to go through doc team to know what links they want us to point at. @jinujoseph @kendrahavens @mikadumont do you know who would be a good contact there to ask about this?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think it's a big deal. I even don't know how it matters if it's dev16 or dev15 or whatever version. Both redirects to the correct page.

I'd prefer not to have any version at all. Errors from the C# compiler are not really version specific.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@CyrusNajmabadi The docs team currently relies on f1_keywords metadata that exists in articles. Because the error messages documentation is scattered in two different folders currently, I don't think there is another way.

AFAIK, the docs team has an internal request to support a whole folder redirection, which will make it easy to have all error messages in one folder.

I'll let @BillWagner or @adegeo confirm that.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, I will work with @kexugit about the new name and update you soon.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We will deploy this change after the Ignite event ends.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Youssef1313 The change has been deployed. You can go ahead and update the PR. Thanks to @OsmondJiang 's team!

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Youssef1313 Youssef1313 requested a review from a team as a code owner September 30, 2020 15:44
@Youssef1313 Youssef1313 changed the title Fix F1 help link for C# error messages Fix F1 help link for error messages Sep 30, 2020
@Youssef1313
Copy link
Member Author

@333fred Build is green. Can you review?

Copy link
Member

@333fred 333fred left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM (commit 17). @dotnet/roslyn-compiler for another review.

@333fred 333fred added the Community The pull request was submitted by a contributor who is not a Microsoft employee. label Oct 1, 2020
@333fred
Copy link
Member

333fred commented Oct 5, 2020

@dotnet/roslyn-compiler for a second review.

@jcouv jcouv self-assigned this Oct 6, 2020
Copy link
Member

@jcouv jcouv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM Thanks (iteration 17)

@jcouv jcouv merged commit 3263a2f into dotnet:master Oct 6, 2020
@ghost ghost added this to the Next milestone Oct 6, 2020
@jcouv
Copy link
Member

jcouv commented Oct 6, 2020

Merged/squashed. Thanks @Youssef1313 !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Compilers Community The pull request was submitted by a contributor who is not a Microsoft employee.
Projects
None yet
9 participants