feat(macros): permit passing custom derives to Model or ModelEx

[mcitem]

PR Info

• Closes Applying custom derive macros to ModelEx #2884

New Features

• Permit passing custom derives and attributes to Model or ModelEx.

Motivation

This change allows for granular control over the attributes on both Model and ModelEx. For instance, it enables users to customize the generated TypeScript interface names when using ts-rs with ModelEx.

Usage

#[sea_orm::model]
#[derive(TS, ...)]
// Apply attributes specifically to the generated Model struct
#[sea_orm(model_attrs(ts(rename = "Fruit")))]
// Apply attributes specifically to the generated ModelEx struct
#[sea_orm(model_ex_attrs(ts(rename = "FruitEx")))]
struct Model {
    // ...
}

The code above expands to:

// ...
#[derive(TS, ...)]
#[ts(rename = "Fruit")]
struct Model {
    // ...
}

// ...
#[derive(TS, ...)]
#[ts(rename = "FruitEx")]
struct ModelEx {
    // ...
}

---

• Full Example: SeaORM 2.0 and ts-rs Integration
• ts-rs does not yet support HasOne and HasMany relations for SeaORM 2.0. We are currently waiting for the official release of SeaORM 2.0.

[tyt2y3]

Thank you, I think the design is nice

[tyt2y3]

thank you. can you add a test case under tests, like https://github.com/SeaQL/sea-orm/blob/master/tests/derive_iden_tests.rs ?

we can call it derive_model_tests. we don't have to use the actual ts-rs crate, may be some built-in derive macros like Hash can work too?

[mcitem]

thank you. can you add a test case under tests, like https://github.com/SeaQL/sea-orm/blob/master/tests/derive_iden_tests.rs ?

we can call it derive_model_tests. we don't have to use the actual ts-rs crate, may be some built-in derive macros like Hash can work too?

Thanks for the suggestion! I have added the test case in tests/derive_model_tests.rs as requested.

Regarding the derive macros, I chose to use serde(rename_all = "...") for the following reasons:

Practical Validation: It effectively demonstrates that model_attrs and model_ex_attrs can correctly pass nested attributes to the generated structs, which is a primary use case for this feature.

No New Dependencies: Since serde and serde_json are already used in existing tests , this doesn't introduce any new external dependencies to the workspace.

[tyt2y3]

very cool, thanks again!