You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From the "Chores" menu it would be nice to have the possibility to assign more than one barcode per chores, making it possible to specify the User who execute the chore
Grocy API have the possibility to specify which user did the chore
It seams to work, but didn't do any proper testing, and writing this I can already see a problem if the choreUserId is null.
I didn't check the UI, I made all changes in the DB manually, finding userIDs as well, I don't know how much work it would be to catch all users from Grocy to be able to assign each barcode to a user on the UI
SQL
CREATETABLEChoreBarcodes(
id INTEGERPRIMARY KEY,
choreId INTEGER , #not unique anymore
barcode TEXTNOT NULL , #shoudn't it be unique btw?
choreUserId INTEGER#new column
);
From the "Chores" menu it would be nice to have the possibility to assign more than one barcode per chores, making it possible to specify the User who execute the chore
Grocy API have the possibility to specify which user did the chore
I could quickly make it work with a few changes on
incl/processing.inc.php
andincl/api.inc.php
and the structure of the tablebarcodebuddy.db/ChoreBarcode
It seams to work, but didn't do any proper testing, and writing this I can already see a problem if the choreUserId is null.
I didn't check the UI, I made all changes in the DB manually, finding userIDs as well, I don't know how much work it would be to catch all users from Grocy to be able to assign each barcode to a user on the UI
SQL
incl/processing.inc.php
incl/processing.inc.php
The text was updated successfully, but these errors were encountered: