Closes#65.
There's still some work to be done. With the changes in this PR, this project's
Makefile is a bit of a hybrid between the approaches in the Makefiles of
status-desktop and nim-status. In the future, as this project's tests expand in
scope, the logic in the Makefile, `nim_status_lib.nimble`, and/or
`.github/workflows/test.yml` may need to be revised.
abstract backend; add mock backend and testing
move bookmarks to backend wrapper
move bookmarks to backend wrapper
move bookmarks to backend wrapper
working version
cleanup
add mock backend
add nimble task & test folder
add evn.sh
make test run; implement bookmark method in the mock
add nim unit test
removing duplicated statement that was causing tests to run twice
re-enable other initilizations in the status object; support specifying backend in the constructor
update bookmark test
update bookmark test
update nimble and makefile
update nimble and makefile
update bookmarks test
remove old browser file
fixes#3659
Wallet2 needs its own event otherwise they wallet1/2 mixes
and as not everything is implemented in wallet2, it crashes
In this particular case, the account is added into wallet1 but trigger
an event intercepted by wallet2, wallet2 doesn't have the new account
and crash
This check is here, because of issue#3490, that was happening due to different
messages' order (received from status go). We were emitting always a message on
index 0, what in some cases was not the reply message (doesn't contain "responseTo"
value). This should be handled in status-go but since that part is used by mobile
also and it is working for them, change is applied here.
Fixes: #3490
* refactor: move eth logic out of libstatus wrapper
* move signing phrases out of status go wrapper (libstatus)
* move logic related methods out of libstatus
move logic related methods out of libstatus
move logic related methods out of libstatus
fix sorting
Deserialization was attempting to deserialize via snake case, however the `json` definitions in status-go are using camel case.
The odd thing here is that when *serializing*, status-go expects the fields to be snake cased. Ideally, these should be consistent so that we can use both `Json.encode` and `Json.decode`.
Richard Ramos
Anthony Laibe
Michael Bradley
Andrei Smirnov
Iuri Matias
saledjenic
Eric Mastro
Khushboo-dev-cpp
Eric Mastro
Andrei Smirnov