Update client to support new pending pay table

eosdac / eosdac-client-legacy

This is the frontend to interact with the DAC smart contracts.

MIT License

14 stars 19 forks source link

Closed michaeljyeates closed 5 years ago

michaeljyeates commented 5 years ago

Read both pendingpay and pendingpay2 tables when checking for outstanding pay.

Check the due_date property if it is from pendingpay2 and do not display if it is in the future (or show as pending).

Claiming pay will be the same, no matter which table it came from

michaeljyeates commented 5 years ago

pendingpay should read from the scope of the contract, the new table is read from the dac_id scope.

There is some data in jungle in the old table with the dac_id scope, ignore these