Skip to content
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

IntelliSense results for command names should be sorted alphabetically #579

Closed
daviwil opened this issue Mar 17, 2017 · 4 comments
Closed
Labels
Issue-Bug A bug to squash.
Milestone

Comments

@daviwil
Copy link
Contributor

daviwil commented Mar 17, 2017

The ISE sorts IntelliSense results alphabetically. The PowerShell extension should be consistent with that.

/cc @dotps1

@daviwil daviwil added the Issue-Bug A bug to squash. label Mar 17, 2017
@daviwil daviwil added this to the 0.10.2 milestone Mar 17, 2017
@rkeithhill
Copy link
Contributor

What sort of IntelliSense? For instance ISE does not alpha-sort parameters e.g.:
image
The common parameters go at the end and even then the non-common parameters aren't sorted alphabetically. I think it puts the required parameters at the top of the list (perhaps sorting on position?).

FWIW parameters used to be sorted alphabetically and we got complaints so we changed the order to be like ISE as described above.

@daviwil
Copy link
Contributor Author

daviwil commented Mar 18, 2017

I was referring to command name IntelliSense, glad that you clarified that.

@daviwil daviwil changed the title IntelliSense results should be sorted alphabetically IntelliSense results for command names should be sorted alphabetically Mar 18, 2017
@rkeithhill
Copy link
Contributor

Ah yeah, the command list could be sorted better. I wish VSCode had support for Intellisense filtering like VS 2017 has now. I could easily see having a filter for applications vs cmdlets/functions vs scripts.

@daviwil
Copy link
Contributor Author

daviwil commented Mar 18, 2017

Yeah, that would be pretty handy. I would guess they'll get around to something like that eventually, seems like most features are only a matter of time ;)

daviwil added a commit to daviwil/PowerShellEditorServices that referenced this issue Mar 21, 2017
This change causes VS Code to preserve PowerShell's original
CommandCompletion result sort order by creating SortText entries for every
completion result, not just parameters.

Resolves PowerShell/vscode-powershell#579.
@daviwil daviwil modified the milestones: 0.11.0, 0.10.2 Mar 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug A bug to squash.
Projects
None yet
Development

No branches or pull requests

2 participants