-
Notifications
You must be signed in to change notification settings - Fork 12
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
Issue with params with multi-line descriptions #1
Comments
Thank you so much! This should have been fixed in e1ea5a0 now :) Can you try, please? |
I just tested this, the result is: Documentation
|
@elifoster Thanks, that looks good! I understand that you might prefer another way of formatting the output, but your test proved that our fix to @sfrenkiel's original problem works correctly. Personally, I prefer
to
for multi-line descriptions where the first version preserves the formatting from the source. You seem to disagree here, however. Do you have some example where your formatting makes more sense? Thank you! |
If the description happens to span multiple lines due to length, that is how it would be formatted in te source. Likewise with method descriptions and class descriptions which j2md already handles this way. That line break should be added for For example /**
* @param a This method parameter is slightly complicated, and
* as such it spans multiple lines.
*/ would be expected to be a single line in the resulting markdown. |
You're right, thanks! What about the following way of formatting the output? Becomes single-line description in Markdown:
Becomes multi-line description in Markdown:
|
Yes that would be more consistent. |
Thanks for putting this tool together, it's been very useful for us. One small issue--
Params that have multiple lines of description result in bad markdown with your tool. Note the following class:
The markdown for method1 is good. In the markdown for method2, the word 'line2' comes before line1. This is a problem for us with params that have very long descriptions.
The text was updated successfully, but these errors were encountered: