Specify serialization for sea-orm-cli-generated time fields

[emmiegit]

sea-orm-cli has a --date-time-crate flag to set which crate to use for date/time types. It also has --with-serde to be able to generate serialization/deserialization for the structs. And it even has --enum-extra-attributes for specify additional attributes (say, #[serde(...)] for modifying how serialization is performed.

However, there does not seem to be a way to add serde attributes per-field. In particular, I would like to be able to consistently set the format my timestamp fields serialize to.

For instance, say I have this model:

#[derive(Clone, Debug, PartialEq, DeriveEntityModel, Eq, Serialize, Deserialize)]
#[sea_orm(table_name = "site")]
pub struct Model {
    #[sea_orm(primary_key)]
    pub site_id: i64,
    pub created_at: TimeDateTimeWithTimeZone,
    pub updated_at: Option<TimeDateTimeWithTimeZone>,
    pub deleted_at: Option<TimeDateTimeWithTimeZone>,
    #[sea_orm(column_type = "Text")]
    pub name: String,
}

However, the default datetime serialize for time is not a format I want to be emitting. I can add with = "time::serde::rfc3339" to fields, but this has to be done manually. Given the large number of timestamp fields in my database schema, it would be very nice if sea-orm-cli could generate these attributes for me.

Basically, I would like the utility to generate this:

#[derive(Clone, Debug, PartialEq, DeriveEntityModel, Eq, Serialize, Deserialize)]
#[sea_orm(table_name = "site")]
pub struct Model {
    #[sea_orm(primary_key)]
    pub site_id: i64,
    #[serde(with = "time::serde::rfc3339")]
    pub created_at: TimeDateTimeWithTimeZone,
    #[serde(with = "time::serde::rfc3339::option")]
    pub updated_at: Option<TimeDateTimeWithTimeZone>,
    #[serde(with = "time::serde::rfc3339::option")]
    pub deleted_at: Option<TimeDateTimeWithTimeZone>,
    #[sea_orm(column_type = "Text")]
    pub name: String,
}

I assume this would require a new feature in sea-orm-cli, but it's possible that there is a combination of flags that I've missed which would enable this.

[sinder38]

Maybe you would enjoy EntityFirst approach more (once it fully comes out)?

Allowing per field attributes would be very inconvenient CLI experience as the codebase grows and amount of per field attributes grows

[emmiegit]

Hmm, I don't think Entity First is right for my needs. I still want to maintain my migration files and have sea-orm-cli generate entities automatically for them.

I can appreciate the complexity of adding many new flags for more specific behavior; maybe the solution is enabling library users to call generate and have custom hooks during generation? Or something like that, which moves the complexity out of the CLI and onto end users who need special behavior.