Runique Admin
Documentation / Runique Admin / Planned features

Planned features

Ideas for future versions of the Runique admin (ModelAdmin builder).

Admin inlines

Edit related models inside the parent form, Django-style:

ModelAdmin::new()
    .form(|f| f.fields([Title, Status]))
    // future:
    // .inline(lines, |i| i.fk(OrderId).fields([Product, Qty]))

The inline would show an editable table (add, remove, update) on the parent's create/edit page.

Public CRUD

Public generic views (in the manner of Django's), with overridable templates. The name is still to choose: view! already exists (GET / POST routing of a handler). Sketch:

crud! { // placeholder name
    Article {
        model: entities::article::Entity,
        prefix: "/articles",
        templates: {
            list:   "articles/list.html",
            detail: "articles/detail.html",
            create: "articles/create.html",
        },
        page_size: 10,
        login_required: true,
    }
}

Target routes: paginated list, detail, create, edit, delete — framework templates overridable block by block, like the admin.

Custom business filters

Today the list scope follows the gate (rights + ownership). A declarative hook for a business filter ("orders in my region") is still open.