status-im
/
status-go
mirror of https://github.com/status-im/status-go.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
status-go/services/accounts
History
yenda 024f30f0b9 Put settings in a table with schema (#1746) 
Move settings table schema from a key-value store to a one row table with many columns.

We now save the first row with initial data in saveAccountAndLogin and follow up saveSetting calls are only saving one setting at a time.

Co-authored-by: Adam Babik <a.babik@designfortress.com>
 		2019-12-27 10:58:25 +01:00
..
README.md Accounts data management (#1530) 2019-08-20 18:38:40 +03:00
accounts.go Start abstracting geth Keystore 2019-12-19 14:11:48 +01:00
multiaccounts.go Replace address with keyUid in accounts db 2019-12-09 11:20:12 +02:00
out.json Add api method settings_getConfigs to retrieve list of configs in a batch quer 2019-08-22 17:32:44 +03:00
service.go Watch new accounts aftter they were saved to accounts table (#1569) 2019-08-28 10:49:03 +03:00
settings.go Put settings in a table with schema (#1746) 2019-12-27 10:58:25 +01:00

README.md

Settings service

Settings service provides private API for storing all configuration for a selected account.

To enable:

  1. Client must ensure that settings db is initialized in the api.Backend.
  2. Add settings to APIModules in config.

API

settings_saveConfig

Parameters

  • type: string - configuratin type. if not unique error is raised.
  • conf: bytes - raw json.

settings_getConfig

Parameters

  • type: string

Returns

  • conf raw json

settings_saveNodeConfig

Special case of the settings_saveConfig. In status-go we are using constant node-config as a type for node configuration. Application depends on this value and will try to load it when node is started. This method is provided in order to remove syncing mentioned constant between status-go and users.

Parameters

  • conf: params.NodeConfig