Fix docs comments in utility folder#7192
Conversation
| /// <param name="endOfRecord"> | ||
| /// this is true if end of record is reached | ||
| /// when delimiter is hit. This would be true if delimiter is NewLine | ||
| /// This is true if end of record is reached |
There was a problem hiding this comment.
I notice in some cases, you merged multiple lines to have a sentence on a single line but in others, such as here, you don't. Is there any particular reason for this?
There was a problem hiding this comment.
I have not set a goal to fix all the problems since there are too many. The main goal is to remove as many problems as possible to kontribjutery not diverted on these messages.
In this case, the IDE performs the formatting themselves when they show this pop-up comment. So deleting strings is better. On the other hand we need to see them on a screen width of 80-120 characters. Although I could miss something-I did not try to catch all the cases.
There was a problem hiding this comment.
Change case: ConvertTo-XML instead of Convertto-XML
There was a problem hiding this comment.
The period doesn't belong here; it breaks the sentence.
There was a problem hiding this comment.
Suggest One-time instead of one time.
There was a problem hiding this comment.
Suggest One-time instead of One time.
There was a problem hiding this comment.
Suggest: remove the empty comments
There was a problem hiding this comment.
Remove added period' it breaks the sentence.
There was a problem hiding this comment.
Suggest: change 'to be add' to ' to add'
There was a problem hiding this comment.
Suggest: I believe these two lines should be one sentence..
...this is ErrorRecord.ErrorDetails.Message; otherwise, the
There was a problem hiding this comment.
Suggest the same as above.... ErrorDetails.Message; otherwise, ...
|
I looked at some of the changes and my primary concern is that adding a period to the end of a |
|
Unfortunately, most public comments are formal and do not do any benefits. We could remove them at all or replace them with a placeholder. Can someone replace all these formal comments with useful ones? It seems not real. So we can just remove the noisy CodeFactor issues formally. Let's do a formal review - we can't replace tons of formal comments with meaningful ones. |
|
@dantraMSFT Your comments was addresed. |
|
@iSazonov looking at some of the original comments in the code, they don't provide value other than get past the compiler error of not having a |
|
@dantraMSFT please take a look again. |
There was a problem hiding this comment.
Capitalize implementation.
There was a problem hiding this comment.
change option to options (plural)
There was a problem hiding this comment.
match the spelling of the Stopprocessing comment with the member name
There was a problem hiding this comment.
Remove the empty comment line.
There was a problem hiding this comment.
use 'one-time' instead of 'one time'
36cb6e2 to
43d3206
Compare
|
@dantraMSFT Your comment was addressed. |
dantraMSFT
left a comment
There was a problem hiding this comment.
There are 3 or 4 items that were missed. Search for ping)
Other than that, LGTM
|
I corrected one pass, the rest well disguised by GitHub. I suppose we can merge as is. |
PR Summary
The PR contains only style changes outside codes. It does not aim to eliminate all style issues - only reduce their number and increase the CodeFactor usefulness.
Changes are distributed by commits to make it easier to review.
PR Checklist
.h,.cpp,.cs,.ps1and.psm1files have the correct copyright headerWIP:to the beginning of the title and remove the prefix when the PR is ready.[feature]if the change is significant or affects feature tests