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

Remove "compiler-option" suffix from file names #20162

Closed
Youssef1313 opened this issue Aug 18, 2020 · 2 comments · Fixed by #22797
Closed

Remove "compiler-option" suffix from file names #20162

Youssef1313 opened this issue Aug 18, 2020 · 2 comments · Fixed by #22797
Assignees
Labels
doc-enhancement Improve the current content [org][type][category] Pri2

Comments

@Youssef1313
Copy link
Member

Youssef1313 commented Aug 18, 2020

https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/compiler-options/langversion-compiler-option

The -compiler-option in the url is an unnecessary duplication. It's better to be just:

https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/compiler-options/langversion

@dotnet-bot dotnet-bot added the ⌚ Not Triaged Not triaged label Aug 18, 2020
@BillWagner BillWagner added doc-enhancement Improve the current content [org][type][category] P2 and removed ⌚ Not Triaged Not triaged labels Aug 25, 2020
@BillWagner
Copy link
Member

@Youssef1313

You're right, but I'm going to advocate for a different change.

I think there is a case for creating one page that lists all the compiler options with a brief description. Each option would be an H2, so the right nav would be useful for finding each option. I think the page length would still be manageable. Finally, it would create one obvious location for explaining how to set compiler options using dotnet build or msbuild.

What do you think?

@Youssef1313
Copy link
Member Author

@BillWagner That looks perfect!

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] Pri2
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants