Skip to content

Apply IDE0019: InlineAsTypeCheck in Management.Automation folders - #19692

Merged
Dongbo Wang (daxian-dbw) merged 6 commits into
PowerShell:masterfrom
Molkree:ide0019-management-automation-1
Jul 11, 2023
Merged

Dongbo Wang (daxian-dbw) merged 6 commits into
PowerShell:masterfrom
Molkree:ide0019-management-automation-1

Conversation

@Molkree

@Molkree Dmitrii Volodin (Molkree) commented May 21, 2023 •

Copy link
Copy Markdown
Contributor

PR Summary

Fix IDE0019 in Management.Automation folders, including cimSupport, DscSupport, logging, security, singleshell, utils.

PR Context

#18399
https://docs.microsoft.com/dotnet/fundamentals/code-analysis/style-rules/ide0019
Microsoft.CodeAnalysis.CSharp version 4.6.0-1.final.
There might have been some manual fixes in this PR but they all fall into 3 categories:

  1. Newly created double newlines that trigger other diagnostics.
  2. Code that previously looked like this
    if (condition)
    {
        Type type = var as Type;
        if (type != null)
        ...
    was fixed to this:
    if (condition)
    {
        if (var is Type type)
        ...
    and I have additionally changed it to this:
    if (condition && var is Type type)
    {
        ...
  3. Once or twice autofix "ate" comments but it might have been in another PR. You can see all similar PRs in the linked issue.

PR Checklist

cimSupport, DscSupport, logging, security, singleshell, utils
@iSazonov Ilya (iSazonov) added the CL-CodeCleanup Indicates that a PR should be marked as a Code Cleanup change in the Change Log label May 25, 2023
@ghost ghost added the Waiting on Author The PR was reviewed and requires changes or comments from the author before being accept label May 25, 2023
Co-authored-by: Paul Higinbotham <paulhi@microsoft.com>
@ghost ghost removed the Waiting on Author The PR was reviewed and requires changes or comments from the author before being accept label May 27, 2023
@ghost ghost added the Review - Needed The PR is being reviewed label Jun 4, 2023
@ghost

Copy link
Copy Markdown

This pull request has been automatically marked as Review Needed because it has been there has not been any activity for 7 days.
Maintainer, please provide feedback and/or mark it as Waiting on Author

@SteveL-MSFT Steve Lee (SteveL-MSFT) left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM

@ghost ghost removed the Review - Needed The PR is being reviewed label Jun 26, 2023
@ghost ghost added the Review - Needed The PR is being reviewed label Jul 4, 2023
@ghost

Copy link
Copy Markdown

This pull request has been automatically marked as Review Needed because it has been there has not been any activity for 7 days.
Maintainer, please provide feedback and/or mark it as Waiting on Author

@pull-request-quantifier-deprecated

Copy link
Copy Markdown

This PR has 145 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!


Quantification details

Label      : Medium
Size       : +51 -94
Percentile : 49%

Total files changed: 17

Change summary by file extension:
.cs : +51 -94

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

  • Fast and predictable releases to production:
    • Optimal size changes are more likely to be reviewed faster with fewer
      iterations.
    • Similarity in low PR complexity drives similar review times.
  • Review quality is likely higher as complexity is lower:
    • Bugs are more likely to be detected.
    • Code inconsistencies are more likely to be detected.
  • Knowledge sharing is improved within the participants:
    • Small portions can be assimilated better.
  • Better engineering practices are exercised:
    • Solving big problems by dividing them in well contained, smaller problems.
    • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

  • Use the PullRequestQuantifier to quantify your PR accurately
    • Create a context profile for your repo using the context generator
    • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
    • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
    • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
  • Change your engineering behaviors
    • For PRs that fall outside of the desired spectrum, review the details and check if:
      • Your PR could be split in smaller, self-contained PRs instead
      • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

  • One line was added: +1 -0
  • One line was deleted: +0 -1
  • One line was modified: +1 -1 (git diff doesn't know about modified, it will
    interpret that line like one addition plus one deletion)
  • Change percentiles: Change characteristics (addition, deletion, modification)
    of this PR in relation to all other PRs within the repository.


Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

@daxian-dbw
Dongbo Wang (daxian-dbw) merged commit b679b59 into PowerShell:master Jul 11, 2023
@ghost ghost removed the Review - Needed The PR is being reviewed label Jul 11, 2023
@Molkree
Dmitrii Volodin (Molkree) deleted the ide0019-management-automation-1 branch July 12, 2023 21:26
Thatgfsj (Thatgfsj) pushed a commit to Thatgfsj-contribs/PowerShell that referenced this pull request Aug 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CL-CodeCleanup Indicates that a PR should be marked as a Code Cleanup change in the Change Log Medium PowerShell-Docs not needed The PR was reviewed and doesn't appear to require a PowerShell Docs update

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants