Galapagon
Galapagon
@berrnd Any risks or notes to be aware of if switching this?
> > @berrnd Any risks or notes to be aware of if switching this? > > I don't know what you mean exactly, when you want to expose `userfield_values_resolved` as...
Okay, fair enough, thank you! On Fri, Sep 9, 2022 at 2:38 PM Bernd Bestel ***@***.***> wrote: > If there's no risks or concerns, why is this a modified setup...
Should I report this as an issue directly on SebRut/pygrocy? I'm not sure what I'd include, other than my original testing and Marcelvriend's comment. Thank you
Actually, it looks like it may have already been fixed upstream here, but for some reason was never implimented? https://github.com/SebRut/pygrocy/issues/200
I'm understanding a bit better now, I see the differences between api/objects/chores and api/chores now
Turns out this is a "bug" all the way up at the Grocy level itself. https://github.com/grocy/grocy/issues/1484
@jlsjonas personally, I've been hoping for an integrated dropdown box that would track for whatever user is currently selected from the dropdown. I know I could do visibility based on...
> My suggestion for that would be create one card per user, and use conditional card to choose which one to display based on input_select.grocy_user. That's the common cited solution,...
> 🤔 your idea inspired me to a solution that might work right now (as long as you don't have multiple users operating the dashboard at the same time 😅...