-
Notifications
You must be signed in to change notification settings - Fork 21
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
Allow automatic generation of function signature in function XML comments #1384
Comments
Tooltips should be perfectly capable of displaying the signature without having to put it in the doc comment, manually or automatically. What editor are you using? |
Yeah, I second that. XML docs is usually complimentary to the signature in tooltips in tooling or used in the autogenerated documentation (like we have for fslib). What would be some examples when you need an additional signature in the xmldoc itself? |
My bad! I haven't used tooltips with my own XML docs. I didn't realize
there was a separate mechanism being used to generate the signature in
Visual Studio 2022, which I use. Thanks a lot for your rapid response and
please close the request.
…-- CMD
On Tue, Sep 10, 2024 at 5:10 AM Vlad Zarytovskii ***@***.***> wrote:
Tooltips should be perfectly capable of displaying the signature without
having to put it in the doc comment, manually or automatically. What editor
are you using?
Yeah, I second that. XML docs is usually complimentary to the signature in
tooltips in tooling or used in the autogenerated documentation (like we
have for fslib). What would be some examples when you need an additional
signature in the xmldoc itself?
—
Reply to this email directly, view it on GitHub
<#1384 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKLOHV3LCW6FAHJNHZMQBPTZV2ZQRAVCNFSM6AAAAABN5ZBSSCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBQGEYDGMZTHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
This does vaguely remind me of the perennial haskell style inline sigs generation suggestion. Basically the same as the FSI signatures file but placed prior to each function. The value is slightly low but it could be nice when you're trying to look at code in github. |
Thanks for the tip!
…On Wed, Nov 13, 2024 at 12:09 PM Alan Ball ***@***.***> wrote:
This does vaguely remind me of the perennial haskell style inline sigs
generation suggestion. Basically the same as the FSI signatures file but
placed prior to each function. The value is slightly low but it could be
nice when you're trying to look at code in github.
—
Reply to this email directly, view it on GitHub
<#1384 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKLOHV53SHL6KAWAZSU23XL2AOBTPAVCNFSM6AAAAABN5ZBSSCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZUGIZTMOJVG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
**I propose we allow automatic generation of function signature in function XML comments.
** The signature is the most important piece of documentation and it should be included. The existing way of approaching this problem in F# is to manually write out the signature. Doing this automatically ensures that we save time and get it right.
Pros and Cons
The advantages of making this adjustment to F# are better documentation and saved time.
The disadvantages of making this adjustment to F# are time to implement and an extra line in the function docs.
Extra information
Estimated cost (XS, S, M, L, XL, XXL):
S. Automatic signature generation is already done in FSI, so it should be an easy implementation.
Related suggestions: (put links to related suggestions here)
Affidavit (please submit!)
Please tick these items by placing a cross in the box:
Please tick all that apply:
For Readers
If you would like to see this issue implemented, please click the 👍 emoji on this issue. These counts are used to generally order the suggestions by engagement.
The text was updated successfully, but these errors were encountered: