Using optional with type in 11.x

[GuillaumeDecMeetsMore]

Hello!
First, thank you for providing/working on this lib, it's really helpful for sharing types.

I have a (weird?) use-case that doesn't seem to work in the new v11, and I don't find a good fix/alternative for it.
It's mostly related to the combination of optional with type

In my case, I'm using ts-rs to shared types for the HTTP bodies (JSON) and parameters. The backend is in Rust, and I provide a TS client. For example, in v10, I was doing this

#[derive(Deserialize, TS)]
#[serde(rename_all = "camelCase")]
#[ts(export)]
struct CreateCalendarEventBody {
   /// Start time of the event (UTC)
   #[ts(optional, type = "Date")]
   pub start_time: Option<DateTime<Utc>>, /// Chrono
}

export type CreateCalendarEventBody = {
   /**
   * Start time of the event (UTC)
   */
   startTime?: Date
}

Defining it as a Date instead of the default string for chrono's Datetime works fine here, as the JSON serializer will (implicitly) convert it to a string. Using an optional Date here is unlikely to cause errors, and it makes more sense to the clients of my SDK.

However, in v11, it seems not possible anymore to use type with optional (error type is not compatible with optional).
Using optional_fields with type seems also to remove the optional (which can make sense if we assume type overrides anything)

#[derive(Deserialize, TS)]
#[serde(rename_all = "camelCase")]
#[ts(export, optional_fields)]
struct CreateCalendarEventBody {
   /// Start time of the event (UTC)
   #[ts(type = "Date")]
   pub start_time: Option<DateTime<Utc>>,
}

export type CreateCalendarEventBody = {
   /**
   * Start time of the event (UTC)
   */
   startTime: Date
}

I'm maybe missing something ? Don't hesitate to tell me 🙂

[NyxCode]

Hey, thanks for reaching out!
This looks to me like a regression which wasn't caught by our tests.

The error is raised here, and types::named then checks for overrides first and returns early.

cc @gustavo-shigueo

[NyxCode]

One thing we introduced in that PR was compile-time checking that #[ts(optional)] is only used on a field of type Option<T>, which also interacts poorly with type overrides.

Edit: Ah, I forgot we already had a naive check for this before as well. But maybe we should disable it when #[ts(type)] is present.

[NyxCode]

@GuillaumeDecMeetsMore This regression should be fixed now in v11.0.1

[GuillaumeDecMeetsMore]

Sorry for the lack of answers, got caught up with other things at work.
Thank you for the quick fix ! 👍