hashavshevet-sync-uri-test
v1.0.4
Published
# deploy: create .env file, and add the following: WIZ_KEY={wiz token here} WIZ_COMPANY={company code here}
Downloads
10
Readme
hashavshevet-sync
deploy:
create .env file, and add the following: WIZ_KEY={wiz token here} WIZ_COMPANY={company code here}
BANK_USER_CODE={bank user code here} BANK_PASSWORD={bank password here}
$ npm i
on app.ts you can manage how far back (in months) data will sync. look for: executeSync(2); and change the digit (2 by default) to whatever int you need.
development:
$ npm run dev
fixes awaiting:
bank transaction unique ID: not given by israeli-bank-scrapers. for now, it's defined as string of valuedate+suF, but could happen that two transactions share these same details.
only one account: needed to improve so can collect data from many accounts, and not only "hapoalim"
tests needed
local database creation (with in-app ID)
handling "accountsList" update, instead of replace
handling issued and temporary hashavshevet batches differently
smart algorithm to compare transactions
technical issues:
- how to manage temporary inputs to hashavshevet
- differentiate handling temp and issued batches
- what to do with hashavshevet transactions that doesn't appear in bank accounts?
- response keys with different types handling (examp. ./graphql/types/recordsTransactions => addTransactionsResponsType function)
- add record and transaction errors (from checkBatch) as data in original type