add --with-comments to preserve comments when returning an attribute

[wondersd]

fixes #102

Only returns comments when attribute value is a block. Not sure whats missing to capture inline comments. However for the purposes of the original request this would be close enough

[minamijoyo]

Thanks for working on this. Overall, it looks good, but let me point out a few things.

(1) The linter check is failing. Some files need to be formatted.

(2) Although this cannot be strictly checked in the linter, the Go style convention recommends MixedCaps. That is to say, withComments seems more natural than withcomments for local variable names.

(3) Regarding being unable to get inline comments, they may belong to an attribute rather than an expression. I'll look into this later, but is this essential for your use case? I am unsure if I can find the time to look into it right away.

[wondersd]

Thanks for looking at this. I was going to go with withComments but everything else in the repo seemed to stick to lower so went with withcomments, will change and fix formatting.

For inline comments it doesn't matter for my purposes, i just considered it for completeness sake. If this goes out as is should we consider --with-comments-on-blocks to not make this a breaking change when inline comments are able to be accounted for?

[minamijoyo]

Thank you for the fix! I'll investigate the inline comments issue later, but I believe it would be technically possible without breaking the CLI interface, so there is no need to rename the flag. Let's merge and move forward!

[minamijoyo]

LGTM 👍

[minamijoyo]

@wondersd I've shipped it in v0.2.14 🚀 Thank you for your contribution!

[minamijoyo]

@wondersd FYI: I had time to debug the inline comment issue today and finally figured out how to fix it (#104), released in v0.2.15 🎉