werbies.json is currently keyed by the Etsy store ID. We need to be able to also get the shift4shop ID. The easiest thing to do would probably be to add an optional field to Werbys for shift4shop_id and fill those in. We won't get to index directly into the dict for shift4shop, but performance really is not a concern here for such a small number.
Add a field to each werbies.json with shift4shop's product ID (not sure where to get the product ID, might just need to query the API)
Update wack.py for wacks4shop to be able to grab the werby entry based on shift4shop ID. This will probably entail refactoring announce_new_sales
werbies.json
is currently keyed by the Etsy store ID. We need to be able to also get the shift4shop ID. The easiest thing to do would probably be to add an optional field toWerby
s forshift4shop_id
and fill those in. We won't get to index directly into the dict for shift4shop, but performance really is not a concern here for such a small number.werbies.json
with shift4shop's product ID (not sure where to get the product ID, might just need to query the API)wack.py
forwacks4shop
to be able to grab the werby entry based on shift4shop ID. This will probably entail refactoringannounce_new_sales