[REQ] Allow rewards to be locked/unlocked

[jesserockz]

Feature area

Integration logic/state

Problem or use case

I would like to allow a reward to be manually locked, or locked/unlocked via automations.
I have a reward that I would like my kids to be able to claim 3 times maximum per day.

Proposed solution

Either allow rewards to be manually locked/unlocked wit an action call
or give rewards a maximum claim counter with a schedule for resetting that counter

Expected outcome

Allows for more powerful multiple rewarding of the same item within limits.

Alternatives considered

No response

Additional context

No response

[ccpk1]

I'll give this some thought, there is something similar for enable disable I am probably going to do for chores.

In the meantime, you could do this a few ways. The rewards have detailed attributes for stats like total today. Here are 2 options for automations:

• if approvals on a reward greater then 3 today, use the disapprove reward to send it back
• if approvals on a reward greater then 3 today, use the update reward service to make the cost 99999 which will effectively lock it or just make it more expensive but within reach... you would want a complimentary midnight automation to set it back too

Let me know if that works for the moment.

[jesserockz]

I thought about the first option before posting this but that doesn't show the kids it is "unavailable".
The second should work though for now.

Thanks!

[jesserockz]

Ah, so setting the cost doesn't quite work here as I cannot lock it per child. (They are allowed 3 each).
But I guess at the same time, making a reward lockable manually/via automations also would also lock for all kids.

And you cant assign a reward to only apply to one user AFAICT.

I'll either try come up with something else or maybe implement the first option for now.

Thanks again!

[ccpk1]

Yes, good point that cost / lock is not per user, it is global. Maybe I can work that concept in, but I think it might add more complexity than is warranted. We’ll see when I get some free time to dig into it.

[github-actions]

Fixed in main via PR #162. Marking this issue as release: pending until the next published release ships the change.