diff options
author | Jan Mulder <jlmulder@xs4all.nl> | 2017-08-01 11:38:59 +0200 |
---|---|---|
committer | Dirk Hohndel <dirk@hohndel.org> | 2017-09-04 07:38:30 -0700 |
commit | 190d80e509e24b242024cda28d7caf546250fab1 (patch) | |
tree | 41e53e2f77bc0d6b568bc196964d82a695a61fdc /tests/testgitstorage.cpp | |
parent | b9404b09059095b92147496f2fb4bc07c90faaaa (diff) | |
download | subsurface-190d80e509e24b242024cda28d7caf546250fab1.tar.gz |
mobile: remove superfluous state VALID_EMAIL
This is a no-brainer removal of the VALID_EMAIL state used in QMLManager.
All current usage of this state is "if state is VALID or VALID_EMAIL",
so there is no distinction between the two states.
It is even a little different. The comment suggests "when we can open
a local cloud storage, tied to a cloud account (so explicitly not
the no-cloud status), we have at least a valid email". While this
is formally true, this implies that there is also a cloud account
on the cloud server (ie. the cloud account is in a VERIFIED state).
In other words: currently, there can't exist a valid local storage
that is tied to a valid email adress, without valid cloud account
on the server.
Notice that this touches the discussion on GitHub for commit
e76f527fe530636 (pull request #520). Can we implement the creation
of a valid cloud account without data link to the cloud server?
Currently, we need the server to confirm the email address (for
example for uniqueness reasons on server side). Obviously, we could
hack our way out of this, but we have a perfect solution already
in place. Create a no-cloud account, and transfer that later to
a true and valid cloud account.
Signed-off-by: Jan Mulder <jlmulder@xs4all.nl>
Diffstat (limited to 'tests/testgitstorage.cpp')
0 files changed, 0 insertions, 0 deletions