Peter Cai 236aca3bef api: items/sync: we don't produce uuid_conflict ... `uuid_conflict` only exists because the official implementation uses `uuid` as the primary key for their database, while in ours we use an internal ID and then use (uuid, user) tuple to fetch items. i.e. in our implementation, user A and B can have items that have the same UUID.		2020-02-22 18:51:06 +08:00
..
api.rs	api: items/sync: we don't produce uuid_conflict	2020-02-22 18:51:06 +08:00
item.rs	api: items/sync: always set sync_token to latest ID	2020-02-22 11:49:01 +08:00
lock.rs	only allow one sync per user every time	2020-02-22 10:45:06 +08:00
main.rs	main: remove "extern crate"	2020-02-22 16:46:11 +08:00
schema.rs	drop JWT and use database-based session tokens	2020-02-21 18:57:39 +08:00
tests.rs	tests: add test for email format	2020-02-22 16:47:52 +08:00
tokens.rs	drop JWT and use database-based session tokens	2020-02-21 18:57:39 +08:00
user.rs	main: remove "extern crate"	2020-02-22 16:46:11 +08:00