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
I would like Typescript docs for structs, members, etc., to carry over into the generated Java (and other) code.
E.g. for Typescript like
export interface Foo {
/**
* bar means something that I want to describe.
*/
readonly bar: string;
}
I was expecting the bar means something that I want to describe. description to be carried over to the generated Java code, but it is not. E.g. I was hoping for something like this:
/**
* bar means something that I want to describe.
*/
public Foo.Builder bar(String bar) {
this.bar = bar;
return this;
}
What is the recommended way to reuse documentation from the source Typescript into generated code?
guidanceQuestion that needs advice or information.needs-triageThis issue or PR still needs to be triaged.
1 participant
Converted from issue
This discussion was converted from issue #3326 on March 31, 2022 23:37.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
❓ Guidance
Affected Languages
TypeScript
orJavascript
Python
Java
C#
,F#
, ...)Go
General Information
The Question
I would like Typescript docs for structs, members, etc., to carry over into the generated Java (and other) code.
E.g. for Typescript like
I was expecting the
bar means something that I want to describe.
description to be carried over to the generated Java code, but it is not. E.g. I was hoping for something like this:What is the recommended way to reuse documentation from the source Typescript into generated code?
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions