Crates.io | adminix |
lib.rs | adminix |
version | 0.0.2 |
source | src |
created_at | 2022-01-24 16:52:24.479229 |
updated_at | 2022-01-26 17:06:41.526369 |
description | à la django admin for actix - sqlx |
homepage | https://github.com/julienfr112/adminix |
repository | https://github.com/julienfr112/adminix |
max_upload_size | |
id | 520283 |
size | 3,790 |
see example/
Adminix is implemented with procedural macros. A compile type, it introspects the database and builds routes and handlers for the actix server. These handler are simple crud route implemented with SSR, using the Maud templating library. It use the sqlx query! macro to confirm at compilation time that the queries generated by the macro are compatible with the datase.
Pros :
Cons :
adminix is not an rest API so if you want a now classical back/front architecture, you are on your own
some
A lot of assumption where made :
It's up to the application to ensure authentification. Use gards !
☑ | Basic CRUD |
☑ | sqlite |
☐ | postgres |
☐ | mysql ? |
☑ | foreign key link |
☐ | save nullable (option) |
☐ | foreign key edit |
☑ | reverse foreign key link |
☑ | filter on back |
☑ | smart table in front (sort, filter) |
☑ | home page / template |
☐ | pagination |
☐ | image blob support (readonly) |
☐ | multiple blob file type |
☐ | testing (proc macro + async = 🤔) |
☐ | support non id primary key ? |
☐ | support non id foreign key target ? |
Please, fill issues ! I'm also accepting merge requests, ping me if I'm not reactive enough : ( f"julienfr{ meaning_of_life + 70 }@gmail.com" )