Currently referencing ESDL "types" from ESDL "events" will lead to a build error as the underlying "types" do not implement Serialize/Deserialize and will break the trait derivation for the "event" in question. Example ESDL from my test app lincluded:

aggregate Order {
    order_placed(order_type: String!, line_items: [LineItem!]!, address: Address): OrderPlaced!
    order_status_changed(id: String!, order_status: String!): OrderStatusChanged!
}

event OrderPlaced {
    id: String!
    line_items: [LineItem!]!
    order_type: String!
    order_status: String!
    address: Address
}

event OrderStatusChanged {
    id: String!
    order_status: String!
}

type LineItem {
    item_id: String!
    quantity: Int!
    notes: String
}

type Address {
    address_1: String!
    address_2: String
    city: String!
    state: String!
    zip: String!
}

In this scenario the compiler will puke on the following:

     pub address: std::option::Option<Address>,
     |     ^^^ the trait `Deserialize<'_>` is not implemented for `Address`
     pub line_items: std::vec::Vec<LineItem>,
     |     ^^^ the trait `Deserialize<'_>` is not implemented for `LineItem`
     pub address: std::option::Option<Address>,
     |     ^^^ the trait `Serialize` is not implemented for `Address`
     pub line_items: std::vec::Vec<LineItem>,
     |     ^^^ the trait `Serialize` is not implemented for `LineItem`
     

Use -> separator instead of : for return types.

From:

open_account(initial_balance: Float!): OpenedAccount!

To:

open_account(initial_balance: Float!) -> OpenedAccount!

Adds support for TypeScript code generation.

The project structure is also cleaned up.

Code generation are available under feature flags:

• codegen-rust
• codegen-typescript

Hello, thanks for the thalo initiative, really good project!

Currently the language is strongly opinionated, as a Int is a i64 however we are missing other types such as i16, i32, u16, u32, u64 (for timestamp)

I would like to have the ability to explicit a type from Rust in a ESDL file. As there are multiple languages involved, it would be probably easier to cheat a bit and explicit the primitive types as custom types.

Do you have any idea about this ?