ts_rs and sea-orm

[darkrock]

Hello there!

I am dipping my toes into sea-orm. It can automatically generate structs for database entities, and can take command line arguments to attach ts_rs::TS derives to those models.

However, there is a problem, these structs must be called Model, as there is a whole spider-web of interconnections for sea-orm's derives to work.

Unfortunately this means that when ts_rs is generating typescript files, I end up with a single Model.ts file, which happens to be whichever entity was last generated.

Is there an option, a flag, a feature, that will allow say, the module name of the model to be included within the type name of the exported type? For instance crate::entities::users::Model would be UsersModel.ts with the typescript type of UsersModel.

I have spent a bunch of time seeking an answer and feel lost at this point.

Thanks

[NyxCode]

Hey! I've never used sea-orm, so I'm not actually sure.
The mechanisms we currently have for altering where the file ends up are

• #[ts(rename = "...")] to re-name the type
• #[ts(export_to = "...")] to specify a custom file/directory (defaults to "bindings/{type}.ts")

Maybe the sea-orm CLI can be configured to emit a #[ts(rename = "<table name>")] attribute.
From a brief search, I couldn't find any way to to this, though.

Is there an option, a flag, a feature, that will allow say, the module name of the model to be included within the type name of the exported type? For instance crate::entities::users::Model would be UsersModel.ts with the typescript type of UsersModel.

Not at the moment.
Both the attributes mentioned above need a string literal, so something like #[ts(rename = format!("{}Model", module_path!().rsplit("::").next().unwrap()))] does not work currently.
I suspect this is something we could add in the future, though.

From briefly looking at their CLI, I was surprised to see a few mentions of ts-rs, but no way of including the table name inside custom attributes. The only thing I've found is this very creative script on discord.

I do feel like having the ability to interpolate the table name in sea-orm is a feature they should consider adding - maybe something like --model-extra-attributes 'ts(export, rename = "{table_name}")'.

[NyxCode]

@darkrock I have opened #398, which allows for arbitrary expressions in #[ts(rename)].
I'd appreciate if you could give that branch a try. You can find an example of two ways of doing this here - one where you inline the whole expression in the attribute, and one where you define a macro to do that.

[jtwaleson]

I'm also working with Sea-ORM and ran into this issue. For now I'm just using manual #[ts(rename = ..)].

However, before realizing this was happening, I noticed some random content in the Model.ts when generating the contents, as which definition ends up there was a bit random, due to the race condition.

I don't think it's desirable to have conflicting definitions overwriting the same file, so I've implemented this main...jtwaleson:ts-rs:no-overwrites

A bit sloppy but it is working for me. Would it be a good idea to block this? Then I can polish my implementation and open a PR.