-
Notifications
You must be signed in to change notification settings - Fork 247
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inject comments from .thrift into generated source #218
Comments
@jamesbroadhead I think we do, actually. See the gold file output. This is true across all of the kinds of code we generate, as far as I know. |
@mosesn My guess is that there are places where we miss injecting them. @jamesbroadhead It'd be great if you could enumerate those places where it would help. |
We are seeing a similar problem where comments in thrift definitions are not included in the generated java source code. We are using the scrooge maven plugin:
And our thrift definition looks something like this:
but none of the javadoc is included in the generated files. |
@kuroneko25 I don't think we support javadoc-style (two stars at the beginning), I think we only support c-style (one star at the beginning). Can you try again like so:
It's definitely weird that the one inside the struct doesn't work. We should look into that. |
Moses, I think its only Doc-comment style (/** */) that is converted. But it looks like we don't do this for the generated Java code. Note that A PR to add this for the Java generator would be gladly accepted. On Mon, Jun 27, 2016 at 1:52 PM, Moses Nakamura [email protected]
Kevin Oliver | Twitter, Inc | follow me: @kevino http://twitter.com/kevino |
Whoops, my bad! I think in mainstream thrift, they only do /* */, we should look into supporting that too. |
Often, thrift definitions have useful comments, which are not immediately visible if navigating from code to generated source.
It could be helpful if scrooge generated javadoc-style comments from comments in thrift definitions and injected them into the generated source to help in cases like this.
The text was updated successfully, but these errors were encountered: