rust-csv VS django-tables2

Serde for most of your input and output formats, with the serde-yaml and csv crates for format backends.

If you want to do it in Rust, then you could combine the https://github.com/mjc-gh/rev_lines and and https://github.com/BurntSushi/rust-csv crates.

csv for writing to CSV

Pair that with Serde for serialization/deserialization (JSON, TOML, YAML, CSV/TSV, XML, URL query strings, etc.), Figment for configuration, and ignore for filesystem traversal with blacklist support, and Rust is a real joy for writing CLI utilities.

I had a similar issue and learned that internally tagged enums are not (and apparently can't be) supported: github issue.

Yep, I'll try to have a look at the nesting PR https://github.com/BurntSushi/rust-csv/pull/197 tonight, don't want to be a bitch, and not helping ahah :)

How does this compare to https://github.com/jieter/django-tables2? That one makes it really easy to display database models with column sorting and pagination.

The degree of reusability (Thanks to things like GenericForeignKey and the ubiquity of Django Templates and Django ORM, there are tons of reusable components like django-filter or django-tables)

In Django there is django-tables2 for example, that creates html table from database query.

(eg. "Django apps" like django-filter and django-tables2, which rely on being a slice across the ORM, controller layer, and templating engine.)

From the readthedocs tutorial, A few examples:

I don't see how Axum would enable something like django-tables2 or django-filter which has is vertically integrated with Django's ORM, routing layer, and template system.

I've used actix-web for stuff... but I'm just sick of constantly reinventing the rote boilerplate that things like django-tables2 and django-filter generate for me once I've declared whatever customizations I want.

django-tables2 - like crispy forms but for tables, abstracts away the need to render tables in a template.