Skip to content

Add support for doc comments #399

Closed
Closed

Description

@Jackie-Yang

How to write a function description like this
2016-12-12 9 25 55

Activity

  1. sean-mcmanus commented on Dec 12, 2016

    @sean-mcmanus
    Contributor

    Our extension doesn't currently implement the textDocument/signatureHelp which provides the function "doc-comments". We'll consider possibly adding that in a future release.

  2. guoqingaa commented on Jan 6, 2017

    @guoqingaa

    Hastened to add this feature, the urgent need for this feature.

  3. changed the title [-]How to write a function description[/-] [+]Add support for doc comments[/+] on Mar 2, 2017
  4. guoqingaa commented on Mar 3, 2017

    @guoqingaa

    Another year has passed, do not support this feature, to mention the depressed.
    Add support for doc comments, the urgent need for this feature.

    /* 
    * a doc comments
    */
    
  5. sean-mcmanus commented on Mar 3, 2017

    @sean-mcmanus
    Contributor

    XML doc comments is expected to be supported once signatureHelp is implemented via the IntelliSense engine. The current implementation doesn't support doc comments.

  6. guoqingaa commented on Mar 3, 2017

    @guoqingaa

    Thank you for your reply, but c / c ++ function annotation style support is very necessary in the development of the input code and read the code a lot of help.
    Xml style, such as C #

    /// <summary>
    /// Write the details of the function here
    /// </ summary>
    /// <param name = "out"> description of output parameters </ param>
    /// <returns> description of return value </ returns>
    

    c/c++ style, such as:

    /** brief $ {cursor}
      *
      * Write the details of the function here
      * @param [in] (input parameter description, including the role of each parameter, the value and the relationship between parameters)
      * @param [out] (description of output parameters)
      * @return (description of return value)
      * @see (this function refers to other related functions, here as a link)
      * @note (description of the need to pay attention to the problem)
    */
    
  7. sean-mcmanus commented on Mar 3, 2017

    @sean-mcmanus
    Contributor

    The C/C++ comment should still be supported, but it would appear as just a raw block comment as it does today in Visual Studio 2017 (the XML comments are parsed and the comment for the active param is shown). If you want better support for non-XML comments, it would probably be better addressed via a Visual Studio feedback site, such as https://visualstudio.uservoice.com/forums/121579-visual-studio-ide/category/30937-languages-c , since we're just borrowing their implementation. On 2nd thought, we actually might be able to parse the raw block comment to give the same experience as with XML comments. This won't be done for a while though.

  8. josesimoes commented on Mar 9, 2017

    @josesimoes

    Adding my vote for this. It would be really awesome.

    Question (if this is possible to answer at this time): is the format above (mentioned by guoqingaa) the one that is going to be supported?

  9. sean-mcmanus commented on Mar 9, 2017

    @sean-mcmanus
    Contributor

    As I said in my previous post, all comments would be supported, but only the XML tags will be recognized specially, unless we decide to add additional parsing of the comments.

  10. guoqingaa commented on Apr 17, 2017

    @guoqingaa

    please, the XML tags will be recognized specially at now, thank you.

  11. guoqingaa commented on May 3, 2017

    @guoqingaa

    Nearly half a year, did not put this important function to support, it is really people can not understand, my God ah!

  12. Muny commented on Mar 3, 2018

    @Muny

    Any update on the status of the implementation of this functionality?

  13. sean-mcmanus commented on Mar 5, 2018

    @sean-mcmanus
    Contributor

    @Muny- Unfortunately, it is not on our schedule yet. We listen to the survey feedback to prioritize work (e.g. C/Cpp: Take Survey) so our main focus right now is helping get IntelliSense configured correctly for users. In terms of new features this is about the 3rd most voted issue, when counted as a duplicate of #658 .

  14. 1 remaining item

  15. rei-vilo commented on Mar 7, 2018

    @rei-vilo

    Please also consider the keywords and formatting of Doxygen de facto standard.

    References:

  16. sean-mcmanus commented on Mar 7, 2018

    @sean-mcmanus
    Contributor

    Tomasz (@Misiu) I don't know when we'll start work on doc comments. We don't have a roadmap currently, but you could try asking Rong Lu (@ronglums) for one: https://blogs.msdn.microsoft.com/vcblog/2018/02/20/visual-studio-code-cc-extension-feb-2018-update/ . But VS Code itself doesn't offer much of a roadmap either, from what I can tell: https://github.com/Microsoft/vscode/milestones .

  17. ricardoboss commented on Nov 13, 2018

    @ricardoboss

    Is this discussion still ongoing?

  18. rei-vilo commented on Nov 13, 2018

    @rei-vilo

    I'm afraid this issue would have the same fate as microsoft/vscode#41309.

  19. bobbrow commented on Nov 13, 2018

    @bobbrow
    Contributor

    We are currently developing this feature. The first iteration will not have doxygen support, but that is also on our radar.

  20. aenima1891 commented on Nov 24, 2018

    @aenima1891

    We are currently developing this feature. The first iteration will not have doxygen support, but that is also on our radar.

    Doxygen support would be great!

  21. added
    fixedCheck the Milestone for the release in which the fix is or will be available.
    on Dec 14, 2018
  22. sean-mcmanus commented on Dec 18, 2018

    @sean-mcmanus
    Contributor

    Our latest Insiders vsix has doc comments (no extra support for doxygen though): https://github.com/Microsoft/vscode-cpptools/releases . If you're using VS Code Insiders or have http.proxySupport not set to "off", you might not get the 0.21.0-insiders2 update automatically. And it doesn't work for comments on the right-side: #2936 .

  23. zupalex commented on Jan 25, 2019

    @zupalex

    As I said in my previous post, all comments would be supported, but only the XML tags will be recognized specially, unless we decide to add additional parsing of the comments.

    Hi,

    if I'm correct the doc comment support is now on the main branch. However I do not seem to be able to get the XML tag recognized. I followed the guidelines from this page but when I hover on the function I documented using the

    tag, It displays everything as plain text, including the XML tags.

    vscode_doc

    Did I misunderstand how XML tags are supposed to be parsed or am I missing something?

  24. bobbrow commented on Jan 25, 2019

    @bobbrow
    Contributor

    We don't currently do any special parsing of comment content yet. We will do doxygen first, but I don't think that there is an issue open for XML. Could you open one?

  25. sean-mcmanus commented on Jan 25, 2019

    @sean-mcmanus
    Contributor

    Alexandre Lepailleur (@zupalex) I moved the XML issue to #3097.

  26. locked and limited conversation to collaborators on Oct 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Feature RequestLanguage ServicefixedCheck the Milestone for the release in which the fix is or will be available.

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions