Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Improve hashtable key completion for type constrained variable assignments, nested hashtables and more#17660

Merged
daxian-dbw merged 11 commits into
PowerShell:masterPowerShell/PowerShell:masterfrom
MartinGC94:AddCompletionForTypedVariablesMartinGC94/PowerShell:AddCompletionForTypedVariablesCopy head branch name to clipboard
May 1, 2023
Merged

Improve hashtable key completion for type constrained variable assignments, nested hashtables and more#17660
daxian-dbw merged 11 commits into
PowerShell:masterPowerShell/PowerShell:masterfrom
MartinGC94:AddCompletionForTypedVariablesMartinGC94/PowerShell:AddCompletionForTypedVariablesCopy head branch name to clipboard

Conversation

@MartinGC94

@MartinGC94 MartinGC94 commented Jul 10, 2022

Copy link
Copy Markdown
Contributor

PR Summary

Fixes PowerShell/PowerShellEditorServices#1852
Decided to make a full fix for all hashtable key completion scenarios I could think of:

  • Fixes type inference for ConvertExpressions that use a PowerShell type that hasn't been loaded yet.
  • Fix tab completion for constructor hashtables so it only completes properties if the class has a null constructor or if it's an interface.
  • Fix tab completion for constructor hashtables that use a PowerShell type that hasn't been loaded yet.
  • Fix tab completion for nested hashtables like: Get-WinEvent -FilterHashtable @{SuppressHashFilter=@{<Tab>
  • Fix tab completion for hashtables that are in an array of arguments like: ls | select Name,@{<Tab>}
  • Add the same property completion that exists for type conversions to typed variables command parameters and Property assignments
  • Add completion for the module specification used in using module @{<Tab>

PR Context

PR Checklist

@ghost ghost assigned anmenaga Jul 10, 2022
@ghost ghost added the Review - Needed The PR is being reviewed label Jul 19, 2022
@ghost

ghost commented Jul 19, 2022

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

@iSazonov iSazonov added the CL-General Indicates that a PR should be marked as a general cmdlet change in the Change Log label Jul 20, 2022
Comment thread test/powershell/Host/TabCompletion/TabCompletion.Tests.ps1 Outdated
…e that hasn't been loaded yet.

Fix tab completion for constructor hashtables so it only completes properties if the class has a null constructor.
Fix tab completion for constructor hashtables that use a PowerShell type that hasn't been loaded yet.
Fix tab completion for nested hashtables like Get-WinEvent -FilterHashtable @{SuppressHashFilter=@{<Tab>
Fix tab completion for hashtables that are in an array of arguments like: ls | select Name,@{<Tab>}
Add the same property completion that exists for type conversions to typed variables command parameters and Property assignments
@MartinGC94 MartinGC94 changed the title Add completion for hashtable property definitions for typed variables WIP: Add completion for hashtable property definitions for typed variables Aug 8, 2022
MartinGC94 and others added 2 commits August 9, 2022 21:46
Fix class name as requested by iSazonov
Add enumeration for the inferred types
@MartinGC94 MartinGC94 changed the title WIP: Add completion for hashtable property definitions for typed variables Improve hashtable key completion for type constrained variable assignments, nested hashtables and more Aug 11, 2022
@MartinGC94 MartinGC94 closed this Aug 15, 2022
@MartinGC94 MartinGC94 reopened this Aug 15, 2022
@pull-request-quantifier-deprecated

Copy link
Copy Markdown

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


Quantification details

Label      : Large
Size       : +256 -106
Percentile : 76.2%

Total files changed: 3

Change summary by file extension:
.cs : +191 -77
.ps1 : +65 -29

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.

@iSazonov

Copy link
Copy Markdown
Collaborator

@SeeminglyScience Please review.

@ghost ghost removed the Review - Needed The PR is being reviewed label Dec 14, 2022
@ghost ghost added the Review - Needed The PR is being reviewed label Dec 22, 2022
@ghost

ghost commented Dec 22, 2022

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

@daxian-dbw daxian-dbw 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.

Sorry for taking so long to review. Not finished yet, but want to share feedback so far.

Comment thread src/System.Management.Automation/engine/CommandCompletion/CompletionCompleters.cs Outdated
@daxian-dbw daxian-dbw added the CommunityDay-Large A large PR that the PS team has identified to prioritize to review label May 1, 2023

@daxian-dbw daxian-dbw 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.

I'm fine the use of goto LABEL here to break out of the loop. It's not that confusing to get what it does by reading the code.

@daxian-dbw daxian-dbw merged commit 5605b24 into PowerShell:master May 1, 2023
@ghost ghost removed the Review - Needed The PR is being reviewed label May 1, 2023
@daxian-dbw

Copy link
Copy Markdown
Member

@MartinGC94 Thanks for the contribution and I appreciate your patience.

@andyleejordan

Copy link
Copy Markdown
Member

This is awesome work!

@ghost

ghost commented Jun 29, 2023

Copy link
Copy Markdown

🎉v7.4.0-preview.4 has been released which incorporates this pull request.:tada:

Handy links:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CL-General Indicates that a PR should be marked as a general cmdlet change in the Change Log CommunityDay-Large A large PR that the PS team has identified to prioritize to review Large

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Typed Variables should intellisense hashtable properties

6 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.