Skip to content
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

Open
davglass opened this issue Jun 4, 2012 · 19 comments
Open

@return tag supports complex object #37

davglass opened this issue Jun 4, 2012 · 19 comments
Assignees

Comments

@davglass
Copy link
Member

davglass commented Jun 4, 2012

If a return value is an object with a complex structure, you can nest @param tags underneath the @return value.

@ghost ghost assigned davglass Jun 4, 2012
@HeikoR
Copy link

HeikoR commented Mar 13, 2013

This would be a great feature extension. Spent some time searching google on how to do this until I found this issue.
+1

Thanks for a great tool.

@lukemadera
Copy link

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

@andreu86
Copy link

+1, this would be great

@digitil
Copy link

digitil commented Jul 10, 2013

+1 this would remove the need for awkward workarounds

@lexander
Copy link
Contributor

Is @param the correct idea or does @attribute better capture what is being described?

@qraynaud
Copy link

+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?

@luxocrates
Copy link

+1

This would be monumentally useful.

@lexander
Copy link
Contributor

@qraynaud seems like most people prefer @param (assuming they'd have chimed in if they liked the alternative). So if @attribute would break stuff, we should drop that idea.

@tgirardi
Copy link

+1

1 similar comment
@wbyoung
Copy link

wbyoung commented Aug 26, 2014

+1

@qraynaud
Copy link

@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 ^^.

@okuryu okuryu changed the title Return tag complex object @return supports complex object Dec 23, 2014
@okuryu okuryu changed the title @return supports complex object @return tag supports complex object Dec 23, 2014
@CraigFeldspar
Copy link

+1

@okuryu
Copy link
Member

okuryu commented Jan 22, 2015

Okay, I'll take a look in the near future. 😄

@okuryu okuryu assigned okuryu and unassigned davglass Jan 22, 2015
@anagami
Copy link

anagami commented Sep 9, 2015

Hello!
Have any progress for this issue?

@okuryu
Copy link
Member

okuryu commented Sep 9, 2015

I'm working in progress on this.

@chopper
Copy link

chopper commented Jun 28, 2016

+1 Any update on this?

@qraynaud
Copy link

@chopper it is my understanding that this package is not supported anymore, you should migrate on another one

@chopper
Copy link

chopper commented Jun 28, 2016

@qraynaud YUIDoc in general is not supported anymore?

@qraynaud
Copy link

At least it looks like it yes. But I might be wrong...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests