feat: use loginWithConfig instead of login
This commit is contained in:
parent
caa44cf5b9
commit
4e30c510dd
|
@ -219,7 +219,16 @@ proc login*(name, keyUid, hashedPassword, identicon, thumbnail, large: string):
|
|||
if(thumbnail.len>0 and large.len > 0):
|
||||
payload["identityImage"] = %* {"thumbnail": thumbnail, "large": large}
|
||||
|
||||
let response = status_go.login($payload, hashedPassword)
|
||||
# TODO:
|
||||
# If you added a new value in the nodeconfig in status-go, old accounts will not have this value, since the node config
|
||||
# is stored in the database, and it's not easy to migrate using .sql
|
||||
# While this is fixed, you can add here any missing attribute on the node config, and it will be merged with whatever
|
||||
# the account has in the db
|
||||
var nodeCfg = %* {
|
||||
|
||||
}
|
||||
|
||||
let response = status_go.loginWithConfig($payload, hashedPassword, $nodeCfg)
|
||||
result.result = Json.decode(response, JsonNode)
|
||||
|
||||
except RpcException as e:
|
||||
|
|
|
@ -1 +1 @@
|
|||
Subproject commit b60faf96449cb9ba9c6494abf7a3fcbaa7849c17
|
||||
Subproject commit e579401e2dc489c387ed46c80090cf3d1b050a92
|
|
@ -1 +1 @@
|
|||
Subproject commit abbd796e0c56402e0723c407119cabbb9fbd5d73
|
||||
Subproject commit 059603986c8b11d47ab2def7436354881cb9bff6
|
Loading…
Reference in New Issue