azuredatastudio
azuredatastudio copied to clipboard
microsoft
Issue when re-ordering server groups
- SQL Operations Studio Version: 0.23.6
Steps to Reproduce: When re-ordering server groups using drag and drop in the side explorer (to get into alphabetical order) I accidentally placed one group inside another and couldn't get it back out.
Re-ordering (note added)
Let's say I have groups A, B, C, D. Dragging B all the way down to the bottom below D and drop should reorder groups to A, C, D, B but I don't see it happening.
@topp10 Try this. Drag and drop the group which is accidentally added into another group all the way down to the Object Explorer but still within the side bar area then drop it. Let us know if you could save your group 😄
@erickangMSFT Thanks for your reply. It works now but with one quirk! To make it work the first time I actually had to drag the parent group heading down rather than the child... After that it works as expected by dragging the child group header out from the parent to separate the groups.
@topp10 thanks for checking. It seem there is an odd behavior that reordering is not function as expected. Let's say I have groups A, B, C, D. Dragging B all the way down to the bottom below D and drop should reorder A, C, D, B but I don't see it happening. Let me update the issue with that.
Cool. No worries.
Cheers!
On 8 Dec 2017 17:07, "Eric Kang" [email protected] wrote:
@topp10 https://github.com/topp10 thanks for checking. It seem there is an odd behavior that reordering is not function as expected. Let's say I have groups A, B, C, D. Dragging B all the way down to the bottom below D and drop should reorder A, C, D, B but I don't see it happening. Let me file an issue for that.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Microsoft/sqlopsstudio/issues/167#issuecomment-350316892, or mute the thread https://github.com/notifications/unsubscribe-auth/AHOr-QKYX0hZ6psimV8StKV-fpQFJdxsks5s-WzogaJpZM4Qltfe .
Please also look at https://github.com/microsoft/sqlopsstudio/issues/335 when resolving for related requirements.
This is upstream and dependent on https://github.com/microsoft/vscode/issues/32592
Can I +1 this as I have 30+ connections and my OCD is struggling with the untidiness of my list. I understand I can modify the JSON, but that isn't so simple with so many. Many thanks.
Would also like to +1 this, still appears this hasn't been addressed in 1.35.0. For those of us who are tortured with having to keep up with large lists of connections, this would be a great QoL update to lessen that pain. ;)
Would also like to +1 this, still appears this hasn't been addressed in 1.35.0. For those of us who are tortured with having to keep up with large lists of connections, this would be a great QoL update to lessen that pain. ;)
I can see all of my groups and connections in my settings.json file but how do you reorder them? The order in the file doesn't match the order in the right slide-out panel and I don't see any attributes to set the order. I'm trying to reorder the individual connections within a group not the actual groups themselves. Thanks
I can see all of my groups and connections in my settings.json file but how do you reorder them? The order in the file doesn't match the order in the right slide-out panel and I don't see any attributes to set the order. I'm trying to reorder the individual connections within a group not the actual groups themselves. Thanks
The order should be based on the order in the file, but it may not make a lot of sense just glancing at it. There are two main sections you can edit: "datasource.connectionGroups" and "datasource.connections".
For "datasource.connectionGroups", the order of the child elements should match the order of the groups. The only exception is the "ROOT" object. It doesn't matter where it is, all connections that are not part of a defined group are part of this group and show at the top of the tree. If you're moving things around I would highly suggest making or keeping it the top item. For nested groups, they will appear in the order they are defined under their parent group. If you have a lot of groups, this may be very messy in the config where a group from one higher parent is defined later than a group in a different parent.
For "datasource.connections", the order will also match the order of the servers, but within the groups they are part of. This means it could look out of order as you may have connections from a later group at the top, or a mix between groups next to each other. The important thing is that all connections that reference a specific group ID will appear visually in that group in the order they are listed in this section.
For both sections, the exact order doesn't matter so much as the relative order to other entries. So, rather than doing a bunch of edits, just find an entry you want to move and place it so it's in the right order relative to the next or previous item at that tree level.
When you're done editing the config, you can reload the application window ("Developer: Reload Window" in the Command Palette) or just restart the application to get the new sort order.
I can see all of my groups and connections in my settings.json file but how do you reorder them? The order in the file doesn't match the order in the right slide-out panel and I don't see any attributes to set the order. I'm trying to reorder the individual connections within a group not the actual groups themselves. Thanks
The order should be based on the order in the file, but it may not make a lot of sense just glancing at it. There are two main sections you can edit: "datasource.connectionGroups" and "datasource.connections".
For "datasource.connectionGroups", the order of the child elements should match the order of the groups. The only exception is the "ROOT" object. It doesn't matter where it is, all connections that are not part of a defined group are part of this group and show at the top of the tree. If you're moving things around I would highly suggest making or keeping it the top item. For nested groups, they will appear in the order they are defined under their parent group. If you have a lot of groups, this may be very messy in the config where a group from one higher parent is defined later than a group in a different parent.
For "datasource.connections", the order will also match the order of the servers, but within the groups they are part of. This means it could look out of order as you may have connections from a later group at the top, or a mix between groups next to each other. The important thing is that all connections that reference a specific group ID will appear visually in that group in the order they are listed in this section.
For both sections, the exact order doesn't matter so much as the relative order to other entries. So, rather than doing a bunch of edits, just find an entry you want to move and place it so it's in the right order relative to the next or previous item at that tree level.
When you're done editing the config, you can reload the application window ("Developer: Reload Window" in the Command Palette) or just restart the application to get the new sort order.
That worked!
(Hopefully, in a future release, they'll add drag-and-drop support)
