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

[BUG] Items are always placed above widget within a section despite the order in the config #1362

Closed
5 tasks done
Antiz96 opened this issue Oct 25, 2023 · 3 comments
Closed
5 tasks done
Assignees
Labels
🐛 Bug [ISSUE] Ticket describing something that isn't working

Comments

@Antiz96
Copy link

Antiz96 commented Oct 25, 2023

Environment

Self-Hosted (Docker)

System

Firefox 119.0, Arch Linux, Docker 24.0.6

Version

2.1.1

Describe the problem

Not sure if it is a bug or the intended behavior... If it's the latter, I can open a feature request if you prefer

If there are both items and widgets within a single section, it looks like items are always placed above/before the widgets despite the order in the config:

[...]
- name: Section Name
  icon: icon

  widgets:
  - type: widget1
    options:
      option1: some option
  - type: widget2
    options:
      option1: some option
   
  items:
  - title: item1
    description: item1
    icon: icon
    url: some url

With the above config, the item1 is placed above widget1 and widget2 despite being declared after them in the config file.
I tried using some displayData parameters within the config file but it did not work as it seems to only affect items placement (and not widgets').

The expected behavior could be to preserve the order of the config placement (so widgets before items with the above config) or alternatively having an additional parameter to set the order.
Could be something like:

[...]
displayData:
  sortBy:
    - widgets
    - items
    - [...]
[...]

Additional info

I'm looking for a way to put Glances items below the Glances widgets in the below screenshot:

2023-10-25_11-32

By the way, Dashy's awesome. Thanks for your wonderful work!

Please tick the boxes

@Antiz96 Antiz96 added the 🐛 Bug [ISSUE] Ticket describing something that isn't working label Oct 25, 2023
@github-project-automation github-project-automation bot moved this to Todo in Dashy V3 Oct 25, 2023
@CrazyWolf13
Copy link
Collaborator

CrazyWolf13 commented Nov 1, 2023

I think that is known, I can't just find the issue where it is listed.

@liss-bot liss-bot added the 👤 Awaiting Maintainer Response [ISSUE] Response from repo author is pending label Nov 1, 2023
@Antiz96
Copy link
Author

Antiz96 commented Nov 1, 2023

I think that is known, I can't just find the issue where it is listed.

Oh? I searched if it was already reported but couldn't find it. Really sorry if I missed it :/

@liss-bot liss-bot removed the 👤 Awaiting Maintainer Response [ISSUE] Response from repo author is pending label Nov 2, 2023
@Antiz96
Copy link
Author

Antiz96 commented Feb 4, 2025

Hi,

This issue has been opened for a long time now and it doesn't seem to attract much interest. Since I'm not using dashy anymore, I unfortunately can't even say if it is still relevant, nor provide eventual additional help / information that could be required.

I think it's better for me to close it and let anyone else suffering from this issue (given that it is still currently a thing) or being interested to address it to re-open a new one.

Thanks again for your wonderful work 😺

@Antiz96 Antiz96 closed this as completed Feb 4, 2025
@github-project-automation github-project-automation bot moved this from Awaiting Triage to Done in Dashy V3 Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug [ISSUE] Ticket describing something that isn't working
Projects
Status: Done
Development

No branches or pull requests

4 participants