You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Hi, I'm using this crate via the qubit, which has ts-rs with default features enabled.
I describe the issue here, but I think it might be nicer to have this crate support the behavior instead. Unless it does, and qubit is doing something under the hood to prevent this?
Describe the solution you'd like
Even with the serde feature enabled it would be nice if the ts tag could overwrite the serde tag.
For example:
This would be nice in cases where on the rust side I'm fetching data, and then sending it to the typescript side. Where the latter the linter yells at me for not using camel case.
Describe alternatives you've considered
I'm not sure. This could be done with the serde-compat feature disabled I imagine? But that might have other awkward implications.
Additional context
I'm being a bit concise here, because most of my information is in the linked issue on qubit.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Hi, I'm using this crate via the qubit, which has
ts-rs
with default features enabled.I describe the issue here, but I think it might be nicer to have this crate support the behavior instead. Unless it does, and
qubit
is doing something under the hood to prevent this?Describe the solution you'd like
Even with the serde feature enabled it would be nice if the
ts
tag could overwrite theserde
tag.For example:
This would be nice in cases where on the rust side I'm fetching data, and then sending it to the typescript side. Where the latter the linter yells at me for not using camel case.
Describe alternatives you've considered
I'm not sure. This could be done with the
serde-compat
feature disabled I imagine? But that might have other awkward implications.Additional context
I'm being a bit concise here, because most of my information is in the linked issue on qubit.
The text was updated successfully, but these errors were encountered: