[GH-ISSUE #816] [Feature] Persistent Stacks sorting #3585

New Issue

GiteaMirror · 2026-04-13T15:05:50-05:00

GiteaMirror commented

2026-04-13 15:05:50 -05:00

Originally created by @rory-brenan on GitHub (Sep 6, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/816

I like to sort Stacks alphabetically. At the moment this sorting does not persist between page loads so I have to re-sort every time.

Originally created by @rory-brenan on GitHub (Sep 6, 2025). Original GitHub issue: https://github.com/moghtech/komodo/issues/816 I like to sort Stacks alphabetically. At the moment this sorting does not persist between page loads so I have to re-sort every time.

GiteaMirror added the enhancement label 2026-04-13 15:05:50 -05:00

GiteaMirror commented

2026-04-13 15:05:52 -05:00

@MP-Tool commented on GitHub (Sep 7, 2025):

I like to sort Stacks alphabetically. At the moment this sorting does not persist between page loads so I have to re-sort every time.

Hey @rory-brenan! 👋

We've implemented persistent Stack sorting and wanted to clarify what you're looking for exactly.

Current implementation:
✅ Stack sorting (alphabetical, by server, by state, etc.) now persists across page reloads
✅ Works within the same browser/device
✅ Even "unsorted" state is now properly saved

What we're wondering: When you mention "persistent across multiple instances" - do you mean:

Browser tabs/windows (same device, same browser)?
Multiple devices (phone, laptop, etc.)?
Multiple browsers (Chrome on one machine, Firefox on another)?

The current solution uses localStorage, so it works great within the same browser but has some limitations for cross-device/cross-browser scenarios.

Technical note: For true cross-device persistence, we'd need to add a user preferences API to store settings on the server. That's definitely doable but would be a bigger architectural change.

Could you let us know which scenario you had in mind? That way we can make sure we're solving the right problem! 🎯

Thanks for the feature request - really appreciate the feedback!

@MP-Tool commented on GitHub (Sep 7, 2025): > I like to sort Stacks alphabetically. At the moment this sorting does not persist between page loads so I have to re-sort every time. Hey @rory-brenan! 👋 We've implemented persistent Stack sorting and wanted to clarify what you're looking for exactly. **Current implementation:** ✅ Stack sorting (alphabetical, by server, by state, etc.) now persists across page reloads ✅ Works within the same browser/device ✅ Even "unsorted" state is now properly saved What we're wondering: When you mention "persistent across multiple instances" - do you mean: - Browser tabs/windows (same device, same browser)? - Multiple devices (phone, laptop, etc.)? - Multiple browsers (Chrome on one machine, Firefox on another)? The current solution uses `localStorage`, so it works great within the same browser but has some limitations for cross-device/cross-browser scenarios. **Technical note:** For true cross-device persistence, we'd need to add a user preferences API to store settings on the server. That's definitely doable but would be a bigger architectural change. Could you let us know which scenario you had in mind? That way we can make sure we're solving the right problem! 🎯 Thanks for the feature request - really appreciate the feedback!

GiteaMirror commented

2026-04-13 15:05:53 -05:00

@rory-brenan commented on GitHub (Sep 9, 2025):

Hi, thanks for replying!

I think this is partly wrong usage by me, and partly the implementation is not fully robust yet.
When sorted by alphabetical (or reverse alphabetical) order, it persists as expected. My bad.

However, when left to random (there is a - in the column header instead of up or down arrow)... it seems to default into alphabetical sorting. But if I navigate away to a different page of Komodo (e.g. from Stacks to Servers, all within the same browser tab) and then back, it flips to reverse-alphabetical sorting (with up arrow in the column header).

I suspect the state being stored in localStorage is not treating unsorted as a state, so it's reverting to the previous state in the cycle which happens to be reverse-alphabetical.

@rory-brenan commented on GitHub (Sep 9, 2025): Hi, thanks for replying! I think this is partly wrong usage by me, and partly the implementation is not fully robust yet. When sorted by alphabetical (or reverse alphabetical) order, it persists as expected. My bad. However, when left to random (there is a `-` in the column header instead of up or down arrow)... it seems to default into alphabetical sorting. But if I navigate away to a different page of Komodo (e.g. from Stacks to Servers, all within the same browser tab) and then back, it flips to reverse-alphabetical sorting (with up arrow in the column header). I suspect the state being stored in `localStorage` is not treating `unsorted` as a state, so it's reverting to the previous state in the cycle which happens to be reverse-alphabetical.

GiteaMirror commented

2026-04-13 15:05:53 -05:00

@MP-Tool commented on GitHub (Sep 10, 2025):

Okay great then I understand what you want. I have also observed the behaviour you described and you are absolutely right, the unsorted state is currently not saved.

Now that I have a better understanding of what you want, I can start implementing it.

@mbecker20, this issue could be tagged as bug and 1.19.4, I'll later publish the PR.

@MP-Tool commented on GitHub (Sep 10, 2025): Okay great then I understand what you want. I have also observed the behaviour you described and you are absolutely right, the unsorted state is currently not saved. Now that I have a better understanding of what you want, I can start implementing it. @mbecker20, this issue could be tagged as bug and 1.19.4, I'll later publish the PR.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/komodo#3585