dashy Errors when editing through UI

trafficstars

Environment

Self-Hosted (Docker)

System

Synology NAS / Docker

Version

2.1.1

Describe the problem

I posted about this a few days ago but now have more info. I've built a very nice dashboard that runs great. As long as I make all changes through the config file, everything is fine. When I make and save changes through the user UI, It corrupts the config file. I get validation warnings, sections should not have additional property:filtered items. I can see these errors when viewing through the user UI. As long as I don't save the file, the errors won't transfer the config file. The minute I save, then the errors show up in the file. What am I missing?

Additional info

No response

Please tick the boxes

[X] You have explained the issue clearly, and included all relevant info
[X] You are using a supported version of Dashy
[X] You've checked that this issue hasn't already been raised
[X] You've checked the docs and troubleshooting guide
[X] You agree to the code of conduct

Nov 12 '23 18:11 LarryT8959

If you're enjoying Dashy, consider dropping us a ⭐
_{🤖 I'm a bot, and this message was automated}

Nov 12 '23 18:11 liss-bot

I am using docker also and this isn't a permissions problem for myself. I just wanted to add to this. If we are editing boolean in the UI >> Config >> Edit Config, and first option is Write Changes to Config File, we click okay and greeted by a success message in green. However nothing changes when viewing the file in terminal. But... if you are to Preview Changes after this step, the dashboard displays in editing mode, and then with a further save here, you should be able to Save to Disk which will (in my case) update the config file which I have mapped as per:

    volumes:
      - /volume1/docker/dashy/my-config.yml:/app/public/conf.yml

So yeah the property:filtered items bug is the main issue here which I am experiencing. Just thought I would add to this because property:filtered items and writing to the config file is coming back after each rebuild and it seems the rebuild process is not in-line with the UI or yml either.