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

Duplication of C# and VB compiler messages and folders #1491

Closed
BillWagner opened this issue Feb 2, 2017 · 7 comments
Closed

Duplication of C# and VB compiler messages and folders #1491

BillWagner opened this issue Feb 2, 2017 · 7 comments
Labels
doc-enhancement Improve the current content [org][type][category] dotnet-csharp/svc dotnet-visualbasic/svc errors-warnings/subsvc Pri3 won't fix Issues that were closed as part of automated backlog grooming
Milestone

Comments

@BillWagner
Copy link
Member

BillWagner commented Feb 2, 2017

The C# compiler error messages are located in two different directories.

/docs/csharp/misc and /docs/csharp/language-reference/compiler-messages.

They should all be in the 2nd directory, and we need to update the F1 help for Visual Studio to point to the correct location.

The same is true for VB:

/docs/visual-basic/misc

/docs/visual-basic/language-reference/error-messages

/cc @Pilchie

@Pilchie
Copy link
Member

Pilchie commented Feb 2, 2017

VS doesn't point to a directory - we just push the error message id, and the F1 help service does a lookup on the server.

@mairaw
Copy link
Contributor

mairaw commented Feb 2, 2017

It would be interesting to talk with Bill Chiles and see if he knows why this was split. I see some that are in misc and not in compiler-messages and vice-versa. F1 help should just work since the F1 metadata is already present in the topics.

@mairaw mairaw added this to the Backlog milestone Feb 13, 2017
@mairaw mairaw added the update label Feb 13, 2017
@BillWagner BillWagner added Area - C# Guide doc-enhancement Improve the current content [org][type][category] labels Jul 18, 2017
@mairaw mairaw added P2 help wanted Good for community contributors to help [up-for-grabs] labels Feb 15, 2018
@rpetrusha
Copy link
Contributor

When we move the files out of the misc directories, we can do a global redirect of all docs//misc URLs rather than add them one-by-one into the redirects file.

@BillWagner BillWagner added Pri0 Indicates issues or PRs that are critical priority P1 and removed P2 Pri0 Indicates issues or PRs that are critical priority labels Jun 29, 2018
@BillWagner BillWagner changed the title Duplication of C# compiler messages Duplication of C# and VB compiler messages and folders Jul 2, 2018
@Youssef1313
Copy link
Member

One limitation I know that prevents to just easily move the files from one directory to another is that relative links may get broken. Are there other limitations to consider if I want to work on this issue ?

@rpetrusha , @BillWagner, @mairaw

@BillWagner
Copy link
Member Author

@Youssef1313 A quick search says there aren't a lot of relative links among these files.

The volume of files to move means the redirection fie will get a bit out of control, but by being careful we can manage it moving files in blocks of 10 - 20.

@BillWagner BillWagner removed the help wanted Good for community contributors to help [up-for-grabs] label Mar 5, 2020
@IEvangelist IEvangelist added P2 and removed P1 labels Jul 20, 2020
@IEvangelist
Copy link
Member

Can we consolidate / categorize these messages into groups?

Problem statement:

  • All the compiler message docs are low traffic
  • They're not in the TOC
  • Why are they in two different directories

De-prioritize

@BillWagner BillWagner added the won't fix Issues that were closed as part of automated backlog grooming label Jan 21, 2021
@BillWagner
Copy link
Member Author

This issue has been closed as part of the issue backlog grooming process outlined in #22351.

That automated process may have closed some issues that should be addressed. If you think this is one of them, reopen it with a comment explaining why. Tag the @dotnet/docs team for visibility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc-enhancement Improve the current content [org][type][category] dotnet-csharp/svc dotnet-visualbasic/svc errors-warnings/subsvc Pri3 won't fix Issues that were closed as part of automated backlog grooming
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants