Update Badges repeat on all custom entries

[galloween]

Update Badges repeat on all custom entries

[dmyoung9]

I can confirm the same behavior:

This is in the Android app, so they aren't cut off (because the sidebar is expanded), but I am definitely having that badge on all my custom items.

[dmyoung9]

Correction: This is behaving slightly differently for me on PC (Chrome) that in is in the Android app.

It isn't showing on every single custom icon, but it is on a couple, so I'm not sure what's the determining factor.

[dmyoung9]

@galloween Any ideas on how to solve this?

[ianwitherow]

This was bothering me. I can submit a PR but I haven't been seeing much communication or activity on this repo by the author so it might go unmerged. (Edit - never mind, clearly wasn't looking in the right place! @galloween Let me know if you'd like me to submit a PR, or if you'd rather address this a different way)

The problem is that when you add a new item it clones an existing item, modifies it, then appends it. If the cloned item has a badge, the new item will too.

Here's my fix:

• Edit your custom-sidebar-v2/custom-sidebar-v2.js file (I'm using HACS and mine was in www/community)

• Find the function createItem (should be around line 277)

• Anywhere in the if (cln) {} block, add this:

        if (config_entry.new_item) {
          // If the cloned item has a configuration badge, remove it.
          cln.querySelector(".configuration-badge")?.remove();
        }

E.g.,

This will ensure any items that you're adding (instead of moving around) will not have the number badge.

Side note: I struggled with getting Home Assistant to serve up a current version of the custom-sidebar-v2.js file instead of feeding me a cached copy (tried hard refreshing, clearing cache, restarting HA; always got the original copy). I ended up changing the .js filename (and updating the reference in my configuration.yaml's extra_module_url). If someone could tell me how to actually clear the cache for that I'd appreciate it! I'm using HACS which might have something to do with it.

Second edit: Re-reading the original message in this issue, I'm wondering if this can happen to folks even when an item isn't flagged with "new_item": true. If this is the case, we could instead add another option to the entry items such as "badge": false. Just a thought.

[n00bcodr]

I just added your forked repo.
I think it only shows on "new_item". But will test it and see if it is showing on all the entries.

[n00bcodr]

@ianwitherow do you plan to maintain your fork? 😄
This breaks on the latest HA release (2023.4)