microsoft / microsoft/vscode-mssql
[Feature Request]: Allow alternative sorting of Connections/Connection Groups
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 610
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 97
Description
### Feature Description
I would like to be able to sort connections and connection groups in an order other than alphabetical.
### Problem and Motivation
Personally I use the Groups for different environments and it would be helpful to be able to sort them by precedence. Currently it is ordered: "Dev", "Pre-Prod", "Prod", "UAT" which is a bit odd.
Similarly, but probably less important, ordering the connections within the group would also be helpful.
### Related Area
- [x] Connection dialog (SQL Server | Azure browse/Fabric browse)
- [ ] Query editor
- [ ] Query results panel
- [ ] Object Explorer
- [ ] GitHub Copilot integration
- [ ] Preview/Edit data
- [ ] Table Designer
- [ ] Schema Designer
- [ ] Schema Compare
- [ ] Local SQL Server Container provisioning
- [ ] SQL database in Fabric provisioning
- [ ] DACPAC/BACPAC export/import
- [ ] SQL Database projects
- [ ] Query Plan Visualizer
- [ ] Other (please describe below)
### If you selected "Other", please describe the area
_No response_
### Confirmation
- [x] I have searched existing feature requests and couldn't find a match
- [ ] I want to help implement this feature
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the connection dialog for SQL Server, Azure browse, and Fabric browse, and trace how connections and connection groups are currently ordered alphabetically. Define and implement a user-controlled ordering for groups and, if in scope, connections within groups; done means the selected order is reflected consistently in the dialog.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- database, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100