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
Change help to use hyphen switches and consistent casing #3785
Conversation
7bbfc37
to
593c9cc
Compare
0ade69a
to
7e40640
Compare
if (i == 0) | ||
{ | ||
if (helpMessageLines[i].Trim().StartsWith("/") || helpMessageLines[i].Trim().StartsWith("@")) | ||
if (trimmedLine.StartsWith("/") || trimmedLine.StartsWith("-") || trimmedLine.StartsWith("@")) |
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.
This unit test only tests our usage text. I think you should remove the StartsWith("/")
so that we make sure all usage messages are correct
if (item.Key.Contains("Examples")) | ||
{ | ||
// Examples require a certain number of leading spaces | ||
Assert.True(helpMessageLines[i].StartsWith(examplesLeadingSpaces), $"Line {i + 1} of '{item.Key}' should start with '{examplesLeadingSpaces}'."); | ||
} | ||
else if (helpMessageLines[i].Trim().StartsWith("/") || helpMessageLines[i].Trim().StartsWith("@")) | ||
else if (trimmedLine.StartsWith("/") || trimmedLine.StartsWith("-") || trimmedLine.StartsWith("@")) |
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.
Same here
7e40640
to
05baa38
Compare
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 think this looks good. My only question is: should we support and then suggest using --longForm
arguments (with double dashes) or just stick to single-dash/slash everywhere?
I also feel like it's probably worth adding a sentence in the /?
help text that says "switches can be specified with either an initial - or an initial /".
not sure. roslyn doesn't do that. |
Added a commit with explanatory comment on switch usage:
or should this rather be in the description part? |
03f1927
to
2938050
Compare
src/MSBuild/Resources/Strings.resx
Outdated
4) all verbosity levels and their short forms e.g. quiet, or q | ||
LOCALIZATION: None of the lines should be longer than a standard width console window, eg 80 chars. | ||
</comment> | ||
</data> | ||
<data name="HelpMessage_3_SwitchesHeader" UESanitized="true" Visibility="Public"> | ||
<value>Switches: | ||
<value>Switches: Note that you can spefiy switches using both |
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.
typo: specify
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.
thx, fixed
2938050
to
d106cee
Compare
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.
Thanks!
Is the CLA bot expected to work? I should have a valid CLA unless it changed in the last days |
CLA-bot has been crabby lately. I used my superpowers to redeliver the webhook and it turned green. |
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.
Looks really good. Thanks for taking the time to do this!
@dasMulli Just FYI I want to hold off on this as it could impact Visual Studio (there are some old tests in there). We're working on getting a stable insertion (for other reasons), once we do I'll merge this. |
@AndyGerlicher @rainersigwald @dfederm Or do you want this to go into exp/net472 since there are new switches ( |
I wouldn't object if you wanted to retarget to exp/net472 and fix up the new switches, but I also wouldn't mind fixing them at merge time. |
Closing/reopening to re-merge and retest post-RI of net472. |
128e688
to
eabfc9c
Compare
eabfc9c
to
ca95ebd
Compare
Rebased and squashed the two original commits onto latest master and added additional changes for graph build command line arguments. |
What's the status on this? waiting for decisions or ready to merge? |
I think I saw your last push and was waiting for tests or something and then forgot about it for two weeks, sorry! Thanks again. |
Also for transparency, we had been trying to avoid changes that weren't strictly necessary and high potential for breaking something (this changed output messages, so might break something) while we worked to get VS updated to 4.7.2 for the first preview of VS 2019. That plus the tools version change to |
@rainersigwald I really appreciate that you just tell it like it is and not give some bla bla bullsh*. Not just here but in a lot of places.
My "open source work" is mostly things that are important to me and not necessarily high enough to land on teams' backlogs so I completely understand. |
Changes help texts and explanations in the resource file to:
Fixes #3764, fixes #3765