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
run through all inserts that do not exist, and then apply them
upsertsProcessor:
runs through all upserts and applies them
for upserts, they should be processed in order and the index of the lastProcessed upsert is stored in the processor so that it automatically resumes when we add new stuff
Last TBD question:
The above design will still require a commit and push and deploy to upserts.json, how can we improve this so that just a simple admin api/ui achieves the same purpose?
Answer: Defer to next feature, but the above schema should be sufficient wherever stored
The text was updated successfully, but these errors were encountered:
We have, instead of migrations, a file for each insert/approval as well as a corresponding processor, so for example:
eg:
upserts.json
{
nftid1: {type: nft, upsert: {approved: true}}
factoryid: {type: nftfactory, upsert: {approved: true},
}
inserts.json
{
}
insertsProcessor:
upsertsProcessor:
Last TBD question:
The text was updated successfully, but these errors were encountered: