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

Supports @todo tag #112

Open
jwerre opened this issue Jan 10, 2013 · 12 comments
Open

Supports @todo tag #112

jwerre opened this issue Jan 10, 2013 · 12 comments

Comments

@jwerre
Copy link

jwerre commented Jan 10, 2013

Sometimes a class or method needs a little more work. An @todo might be a nice addition.

@dnutels
Copy link

dnutels commented Apr 4, 2013

Supported 👍

@alcidesqueiroz
Copy link

+1

1 similar comment
@ryanrolds
Copy link

+1

@thomaspons
Copy link

+1 really

@dnordstrom
Copy link

+1

Indeed.

Update

Although after a quick search, I notice that @todo is actually already listed in an array of tags in the parser script (on line 167), and described with a comment as 0..n things to revisit eventually (hopefully).

Perhaps it's implemented; I haven't tested it to find out yet.

@Flowkap
Copy link

Flowkap commented Dec 6, 2013

+1 quite indeed!

@hal-gh
Copy link

hal-gh commented Apr 15, 2014

Please, guys, revisit this. :( +1

@limikael
Copy link
Contributor

Hi,

I have a an implementation for custom tags here:

#222

With this it would be possible to create support for different kind of tags as "plug-ins" , either on project level to separate code as @client or @server for example, or @internal or @external. It would also be possible to create reusable tags such as @todo, which would not have to be put in the core of yuidoc, but rather as a reusable and installable plug-ins.

Please take a look and if you like it give it some support to get it merged... :) It would be a good thing to have the preprocessor functionality in the main line since it is already used for a couple of projects by several people in the company where I work...

@hal-gh
Copy link

hal-gh commented Apr 17, 2014

@limikael your work on #222 looks really promising, and I think the author, @caridy, agrees. :)

@limikael
Copy link
Contributor

@hal-gh Ah yep, heard back from him so it seems to be progressing. 👍

Also, once it gets merged it would be nice to create a plugin for the @todo tag since it seems to be a requested feature. But I would like to ask, what should the @todo tag actually do?

A suggestion would be that the text from the @todo tag will be included the description for the class/method/property where it appears in italics (don't know exactly what is possible with the theming and so), and then also all the todos for the project would be exported to a suitable xml format for interoperability with other interesting tools. But which xml format and which tools?

And are there more suggestions or ideas related to the todo tag?

@martinambrus
Copy link

I'd suggest to actually create a new tab with all TODOs listed, although I'm not sure how that would work with the plugin stuff. I'd love to see all TODOs in one place and it would probably be more beneficial than seeing them next to items, as you'd still need to search for them - which could be done in an editor as well.

@arw180
Copy link

arw180 commented Oct 21, 2014

+1 for a TODOs tab

@okuryu okuryu changed the title Enhancement: Create a new @ tag for a 'todo' description. Supports @todo tag Dec 23, 2014
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