8 Commits

Author	SHA1	Message	Date
Benedikt Peetz	a9f72e34e6	Build(cargo): Remove wildcard version specification in `Cargo.toml` ... Wildcard version is comparable to selecting a version depending on the result of a dice roll. What I mean with this is, that the version will be selected based on what the specific user already has in their cargo registry. This means that the same codebase will compile wonderfully on one machine but will fail with weird errors like: `the trait 'From<crossterm::event::Event>' is not implemented for 'Input'` on an other one. Additionally crates.io does not accept crates with a bare wildcard version requirement for aforementioned reasons. Lastly using direct versions requirement allows to use `cargo upgrade` to automatically update these requirements to their highest possible value, as determined by SemVer. This works especially well, when adding new dependencies with `cargo add`, as this also adds a direct version requirement.	2023-07-09 10:09:52 +02:00
antifallobst	658f05b8d3	feature (ui - rooms / events): implemented a rooms list area in the UI and live timeline updates on room timeline sync events	2023-07-08 14:45:08 +02:00
antifallobst	dfc87ff937	refactor (architecture): implemented an event based architecture	2023-07-04 18:32:57 +02:00
antifallobst	9fbf112baa	refactor (logger): switched to cli_log	2023-07-01 12:44:11 +02:00
antifallobst	7bd1990eb3	feature (logging): added a logging backend and spreaded a few info log calls over the codebase	2023-06-29 20:17:54 +02:00
antifallobst	2c894e895e	feature (UI): implemented a login screen	2023-06-29 12:36:16 +02:00
antifallobst	e776d8a631	feature (accounts): implemented login with username and password	2023-06-15 19:19:24 +02:00
antifallobst	ff8a6e66eb	initial commit	2023-06-14 23:49:20 +02:00