-
Notifications
You must be signed in to change notification settings - Fork 210
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
@return tag supports complex object #37
Comments
This would be a great feature extension. Spent some time searching google on how to do this until I found this issue. Thanks for a great tool. |
I've been looking for this for a long time! @davglass are there any usage examples or documentation for this? And does this exist for @Property as well? Basically anytime an object is used, it needs nested support - are we always to use @param? Is this how it's used? @return {Object} The return object
@param {String} str1 A string
@param {Object} ob1 A nested object
@param {Number} number1 A number |
+1, this would be great |
+1 this would remove the need for awkward workarounds |
Is |
+1 Also I suppose that @Attribute would be more sensitive but it would require to make the same change on the parameters. That would be breaking a lot... Or should it support both? |
+1 This would be monumentally useful. |
@qraynaud seems like most people prefer |
+1 |
1 similar comment
+1 |
@lexander I don't mind really. I was suggesting this change because technically those aren't params and it can be kind of confusing. But really, it's fine either way with me ^^. |
+1 |
Okay, I'll take a look in the near future. 😄 |
Hello! |
I'm working in progress on this. |
+1 Any update on this? |
@chopper it is my understanding that this package is not supported anymore, you should migrate on another one |
@qraynaud YUIDoc in general is not supported anymore? |
At least it looks like it yes. But I might be wrong... |
If a return value is an object with a complex structure, you can nest
@param
tags underneath the@return
value.The text was updated successfully, but these errors were encountered: