Remove VeresOne.saveDoc() -- will be the responsibility of calling code to store the did doc
Remove VeresOne.saveKeys() -- will be the responsibility of calling code to save keys
Do not automatically call saveDoc and saveKeys when generating a new did doc
Do not automatically call saveDoc and saveKeys when updating a did doc
Currently distinguishes between getLocal() (local did store) and getRemote() (from ledger). Remove that distinction - client code will need to do the equivalent of getLocal().
When retrieving a DID Doc via get() (local or remote), the driver imports private keys (that correspond to the public keys in the doc) from a key store. This will need to be handled by client code.
Pre-req for https://github.com/digitalbazaar/did-io/pull/44. Fixes #29. (Working off of the
fix-browser-supportbranch):VeresOne.saveDoc()-- will be the responsibility of calling code to store the did docVeresOne.saveKeys()-- will be the responsibility of calling code to save keysgetLocal()(local did store) andgetRemote()(from ledger). Remove that distinction - client code will need to do the equivalent ofgetLocal().get()(local or remote), the driver imports private keys (that correspond to the public keys in the doc) from a key store. This will need to be handled by client code.