feature request: obtain lines of the comments

[mimoo]

It'd be nice to get more metadata on each comments. Right now I'm trying to understand what lines a comment start and end on

[pamela-howell]

+1

[vallentin]

I somehow missed this issue. Feel free to elaborate more, whether it's more than just start and end indices, or there's more metadata you'd like.

I actually have a way more robust experimental comment parser implemented, supporting a lot more languages as well.

[mimoo]

I think in general people tend to want to consume that information in two ways: either with a (start, end) tuple or with a (line, col) tuple. Annoyingly libraries can't decide which one to use so often you have to choose one and then convert whatever doesn't fit that format (so if you can provide both format via a flag that's a big plus).

In my specific usecase I want to check if the comments starts with //~ (a special type of comment my library wants to parse). So in this case, this is useful as well.

Finally, in my usecase I also need to figure out the padding used in front of the comment, which can be a pain to recalculate if you don't provide that information :D

[pamela-howell]

Hi Valentin! I am looking to pull out ALL comments from our codebase…currently mostly written in Python, extractable to Markdown to post to Confluence pages. To be more clear, not only the line numbers….the actual comments themselves. From the comment start marker to the end marker. I’m happy to help test your experimental parser, if you’d allow it; provide extensive feedback if you’d like it 😉; and will ask some more questions my side on our code language(s) (codebase has not yet been exposed to me, as the “lowly” documentation person…but it shall be – today! Best regards and I look forward to our potential collaboration/testing! ---Pam Pamela Howell Mobile: 908-432-5854 From: Christian Vallentin ***@***.***> Reply-To: vallentin/comment-parser ***@***.***> Date: Saturday, July 29, 2023 at 9:35 PM To: vallentin/comment-parser ***@***.***> Cc: "Howell, Pamela (CTR)" ***@***.***>, Comment ***@***.***> Subject: [External] Re: [vallentin/comment-parser] feature request: obtain lines of the comments (Issue #1) I somehow missed this issue. Feel free to elaborate more, whether it's more than just start and end indices. I actually have a way more robust experimental comment parser implemented, supporting a lot more languages as well. — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/vallentin/comment-parser/issues/1*issuecomment-1656991022__;Iw!!FEyU5bU!FQJMVpjsm_W7UbMFUBs9ZRJg71LhOlJ2BwawHAcnaALLirgfgSHZkp4Xmmacc5GAvI46SeuRaOtkM5nKoxna0tMGKN0dLQ$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/BBKULDDF6AAD4WGBX7KKJJDXSW255ANCNFSM5U56VAYA__;!!FEyU5bU!FQJMVpjsm_W7UbMFUBs9ZRJg71LhOlJ2BwawHAcnaALLirgfgSHZkp4Xmmacc5GAvI46SeuRaOtkM5nKoxna0tOSdNVWWQ$>. You are receiving this because you commented.Message ID: ***@***.***> ------------------------------------------------------------------------------ CONFIDENTIALITY NOTICE: If you have received this email in error, please immediately notify the sender by e-mail at the address shown. This email transmission may contain confidential information. This information is intended only for the use of the individual(s) or entity to whom it is intended even if addressed incorrectly. Please delete it from your files if you are not the intended recipient. Thank you for your compliance. Copyright (c) 2023 Cigna ==============================================================================