specta

specta copied to clipboard

You should be able to export a TS type without the Serde checking, like how we allow BigInt's to be configurable.

oscartbeaumont

oscartbeaumont

Support `rename_all = "snake_case"` for command fn names

1

nobane

result value and error transpiled to inline

2

I noticed any type passed into a `Result` as value or error does not form into a separate type in the typescript definitions. example code: ```rs #[derive(serde::Serialize, specta::Type)] enum MyValue...

Natejoestev

Remove all `use ::*`

1

It's both bad for semver and also can cause unintended LSP hints. Right now Rust Analyser wants to import `FunctionDataType` from `specta::js_doc::FunctionDataType` not `specta::functions::FunctionDataType`

oscartbeaumont

What should be public or not? Should it's args be a sealed struct or not?

oscartbeaumont

Ability to define "branded" types.

2

I am currently searching for a way to map TypeScript branded types, like https://github.com/kourge/ts-brand cleanly using specta. My current (flawed) approach is: ``` #[cfg_attr(feature = "wasm", derive(specta::Type))] struct Brand

indietyp

https://github.com/serde-rs/serde/pull/2641#pullrequestreview-1732728579 It's not too late to remove it.

oscartbeaumont

Support phase-specific renames

5

I have a type like this: ```rust #[derive(Serialize, Deserialize, specta::Type)] pub struct Package { #[serde(rename(deserialize = "@version"))] pub version: String, } ``` But specta (2.0.0-rc7) raises the error: ``` error:...

willcrichton

Better `TypeId`

4

Hack around the `'static` bound on Rust's built-in `TypeId` to allow the ID to be tied to a compiler intrinsic instead of the implementation location of the macro like it...

oscartbeaumont