Skip to content

Improve path completion #19489

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.

Sign up for GitHub

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

Jump to bottom
Merged
PaulHigin merged 10 commits into from
May 22, 2023
Merged

Improve path completion #19489

PaulHigin merged 10 commits into from
May 22, 2023

Conversation

@MartinGC94
Copy link
Contributor

@MartinGC94 MartinGC94 commented Apr 11, 2023 •
edited
Loading

PR Summary

Refactor of the file path completion code to make it faster and prepare it for some future improvements I have planned (Not replacing variables in input text, user options for controlling sorting behavior and more).

Speed improvements for relative paths are pretty big:

cd C:\windows\System32\
Measure-Command -Expression {TabExpansion2 -inputScript .\}

old: 1.99 seconds
new: 199 ms

Similar improvements are seen in other providers:

cd HKCU:\SOFTWARE\Classes\
Measure-Command -Expression {TabExpansion2 -inputScript .\}

Old: 1.60 seconds
new: 139 ms

Also stopped it from replacing ~ when referring to home so this: ~\Downloads<Tab> no longer turns into: C:\Users\Martin\Downloads\

PR Context

Fixes #4797
Contributes to: #5350

PR Checklist

@ghost ghost assigned PaulHigin Apr 11, 2023
@MartinGC94 MartinGC94 mentioned this pull request Apr 12, 2023
Closed
@ghost ghost added the Review - Needed The PR is being reviewed label Apr 19, 2023
@ghost
Copy link

ghost commented Apr 19, 2023

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 added WG-Engine core PowerShell engine, interpreter, and runtime Needs-Triage The issue is new and needs to be triaged by a work group. CommunityDay-Large A large PR that the PS team has identified to prioritize to review labels May 1, 2023
PaulHigin
PaulHigin suggested changes May 8, 2023
View reviewed changes
@ghost ghost added Waiting on Author The PR was reviewed and requires changes or comments from the author before being accept and removed Review - Needed The PR is being reviewed labels May 8, 2023
@ghost ghost removed the Waiting on Author The PR was reviewed and requires changes or comments from the author before being accept label May 9, 2023
@MartinGC94 @SteveL-MSFT
Update src/System.Management.Automation/engine/CommandCompletion/Comp…
fafcc24 
…letionCompleters.cs

Co-authored-by: Steve Lee <slee@microsoft.com>
MartinGC94 and others added 2 commits May 9, 2023 18:24
PaulHigin
PaulHigin approved these changes May 9, 2023
View reviewed changes
Copy link
Contributor

@PaulHigin PaulHigin left a comment

Choose a reason for hiding this comment

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

LGTM

iSazonov
iSazonov reviewed May 10, 2023
View reviewed changes
iSazonov
iSazonov reviewed May 11, 2023
View reviewed changes
src/System.Management.Automation/engine/CommandCompletion/CompletionCompleters.cs
return sb.ToString();
}

private static void EscapeCharIfNeeded(
Copy link
Collaborator

@iSazonov iSazonov May 11, 2023 •
edited
Loading

Choose a reason for hiding this comment

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

Not for the PR. Maybe useful .Net implementation pattern https://source.dot.net/#System.Text.RegularExpressions/System/Text/RegularExpressions/RegexParser.cs,151

SteveL-MSFT
SteveL-MSFT requested changes May 15, 2023
View reviewed changes
@ghost ghost added the Waiting on Author The PR was reviewed and requires changes or comments from the author before being accept label May 15, 2023
@ghost ghost removed the Waiting on Author The PR was reviewed and requires changes or comments from the author before being accept label May 16, 2023
@pull-request-quantifier-deprecated
Copy link

pull-request-quantifier-deprecated bot commented May 16, 2023

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

Quantification details 

Label      : Extra Large
Size       : +411 -177
Percentile : 86.27%

Total files changed: 4

Change summary by file extension:
.cs : +375 -174
.ps1 : +36 -3

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.

SteveL-MSFT
SteveL-MSFT approved these changes May 22, 2023
View reviewed changes
Copy link
Member

@SteveL-MSFT SteveL-MSFT left a comment

Choose a reason for hiding this comment

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

LGTM

@PaulHigin PaulHigin merged commit 06ab3b1 into PowerShell:master May 22, 2023
@PaulHigin
Copy link
Contributor

PaulHigin commented May 22, 2023 •
edited
Loading

@MartinGC94 Thanks for your contribution!

@daxian-dbw daxian-dbw added CL-Engine Indicates that a PR should be marked as an engine change in the Change Log and removed Needs-Triage The issue is new and needs to be triaged by a work group. labels May 22, 2023
@ghost
Copy link

ghost commented Jun 29, 2023

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

Handy links:

@ghost ghost mentioned this pull request Jun 29, 2023
Closed
@reaching-for-libra reaching-for-libra mentioned this pull request Jul 10, 2023
Closed
5 tasks
@MartinGC94 MartinGC94 mentioned this pull request Jul 10, 2023
Merged
22 tasks
This was referenced Jul 27, 2023
Closed
Closed
@bradwilson
Copy link

bradwilson commented Nov 22, 2023 •
edited
Loading

Also stopped it from replacing ~ when referring to home so this: ~\Downloads no longer turns into: C:\Users\Martin\Downloads\

This is an unfortunate change. It's broken me a lot because those tildes not being replaced means that applications no longer understand paths with it in it. I got a suggestion to use Enable-ExperimentalFeature PSNativePSPathResolution but that is apparently no longer an option.

Is there a way for me to turn this back on? I'm getting super tired of having to retype C:\Users\bradwilson. 😢

(If not, I may have to roll back to 7.3.9 indefinitely to preserve my sanity)

@iSazonov
Copy link
Collaborator

iSazonov commented Nov 22, 2023

@bradwilson Please open new issue to discuss your scenario(s).

@bradwilson bradwilson mentioned this pull request Nov 22, 2023
Closed
5 tasks
@MartinGC94 MartinGC94 mentioned this pull request Nov 28, 2023
Closed
5 tasks
@SteveL-MSFT SteveL-MSFT mentioned this pull request Apr 24, 2024
Merged
22 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@iSazonov iSazonov iSazonov left review comments

@SteveL-MSFT SteveL-MSFT SteveL-MSFT approved these changes

+1 more reviewer

@PaulHigin PaulHigin PaulHigin approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@PaulHigin PaulHigin

Labels

CL-Engine Indicates that a PR should be marked as an engine change in the Change Log CommunityDay-Large A large PR that the PS team has identified to prioritize to review Extra Large WG-Engine core PowerShell engine, interpreter, and runtime

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Tab completion in large folders is very slow

6 participants

@MartinGC94 @PaulHigin @bradwilson @iSazonov @SteveL-MSFT @daxian-dbw