4 Commits

Author	SHA1	Message	Date
Florent	16ebc32611	Add tests for UsersManager (#1149) ... Context HomeDBManager lacks of direct tests, which makes hard to make rework or refactorations. Proposed solution Specifically here, I introduce tests which call exposed UsersManager methods directly and check their result. Also: I removed updateUserName which seems to me useless (updateUser does the same work) Taking a look at the getUserByLogin methods, it appears that Typescirpt infers it returns a Promise<User|null> while in no case it may resolve a nullish value, therefore I have forced to return a Promise<User> and have changed the call sites to reflect the change. Related issues I make this change for then working on #870	2024-09-05 16:30:04 -04:00
Florent	786ba6b31e	Move HomeDBManager to gen-server/lib/homedb (#1076)	2024-07-05 16:02:39 +02:00
CamilleLegeron	61421e8251	Create user last connection datetime (#935) ... Each time the a Grist page is reload the `last_connection_at` of the user is updated resolve [#924](https://github.com/gristlabs/grist-core/issues/924)	2024-07-01 15:13:39 +02:00
Florent	95b2459f25	HomeDBManager refactoration: extract method related to Users management in its own module (#1049) ... The HomeDBManager remains the exposed class to the other parts of the code: any module under gen-server/lib/homedb like UsersManager is intended to be used solely by HomeDBManager, and in order to use their methods, an indirection has to be created to pass through HomeDBManager.	2024-06-18 10:57:06 -04:00