-
-
Notifications
You must be signed in to change notification settings - Fork 79
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
Filter on Empty Values or Any Values #103
Comments
Hi @SolusCado please try Let me know how it works for you! |
Thanks for the quick response! But… it doesn’t seem to work at all. I opened a new browser in incognito mode just to be completely sure I was getting a new version of the script. It’s loading in my browser as upcoming-media-card.js?hacstag=146783593061.
From: MKANET ***@***.***>
Date: Tuesday, December 3, 2024 at 4:14 PM
To: custom-cards/upcoming-media-card ***@***.***>
Cc: Michael Bailey ***@***.***>, Mention ***@***.***>
Subject: Re: [custom-cards/upcoming-media-card] Filter on Empty Values or Any Values (Issue #103)
Hi @SolusCado<https://github.com/SolusCado> please try version 0.6.1. I just updated this repo a few minutes ago with this enhancement. Please note that when upgrading Upcoming Media Card, sometimes, it requires deleting your web browser cache to remove lingering old upcoming media card javascript code after upgrading to the new version.
Let me know how it works for you!
—
Reply to this email directly, view it on GitHub<#103 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEKBIR4VJFGH4WNAGTDYHED2DYNK5AVCNFSM6AAAAABS6KRLI6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJVGU3DGNBTGE>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Honestly, I didnt test this yesterday since I thought I was a pretty straight-forward fix. Can you post the full EXACT card code you're using? Ill see if I can reproduce the issue. |
There isn't much to it: type: custom:upcoming-media-card |
@SolusCado I tried to test this on my setup before uploading version 0.6.2. However, I had no Sonarr shows to test against that currently have no studio defined. Please try it let me know if it works |
I would think any blank filter would be testable, but I'll check it shortly and let you know.
…________________________________
From: MKANET ***@***.***>
Sent: Thursday, December 5, 2024 11:27:03 PM
To: custom-cards/upcoming-media-card ***@***.***>
Cc: Michael Bailey ***@***.***>; Mention ***@***.***>
Subject: Re: [custom-cards/upcoming-media-card] Filter on Empty Values or Any Values (Issue #103)
@SolusCado<https://github.com/SolusCado> I tried to test this on my setup before uploading version 0.6.2. However, I had no Sonarr shows to test against that currently have no studio defined. Please try it let me know if it works
—
Reply to this email directly, view it on GitHub<#103 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEKBIRYRIEBSMJ5EX6BV47D2EDHLPAVCNFSM6AAAAABS6KRLI6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRRGU4TIOJYGQ>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
I dont know why I didnt think of that before. I just tested it. The following works: |
Ok; those still don't work for me - BUT this does: So, if I just leave it blank to the right of studio, it filters out any records with any value at all. So, that's good enough. NOW... is there any way to reverse that? To show a wildcard or something, so that I only get records WITH a studio? |
Glad its working for you. If you have a suggestion on how to reverse this using |
I would like to setup two separate cards, one that shows all items where a specific attribute (Studio) is empty, and one where that attribute has any value at all. I cannot seem to get this to work.
I can use 'sort_by' on the 'studio' attribute to group the items, but I need to put them in separate cards so I can restrict who can see a specific grouping.
Is there any way to specify something like "filter: studio=''" or "filter: studio=empty"? (And conversely, "filter: studio!=''" or "filter: studio!=empty"...)
The text was updated successfully, but these errors were encountered: