-
Notifications
You must be signed in to change notification settings - Fork 158
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
Format #747
Format #747
Conversation
I see!!!! No wonder I hadn't seen the latest versions :) |
Thank you!! |
Were the deletions of For example: (***condition:fsx***)
#if FSX
let a = 4
#endif results in an output .fsx with: let a = 4
#endif Is this from fantomas? |
Fantomas does appear not to restore the comment after a hash directive. |
They weren't intended. @nojaf Did you create a tracking issue for this in fantomas? |
Fixed for this repo via a .fantomasignore entry |
@dsyme, no I didn't. I'm a bit confused here, is this relevant or not? |
Hmmm, I suspect it's quite common to have clarifying comments in this position, I know I do it all the time to clarify what the #endif is closing. We should probably open a fantomas issue and discuss there even if you decide not to fix, so there's a record of it. In this case yes, there's a meaning of sorts for the somewhat hacky pre-processing of the scripts (that however could likely be implemented in other ways) |
This will be painful if we need to check this in larger files: example. Every comment after source code that is not yet assigned should be checked against hash directives. |
Hi @dsyme,
fantomas-tool
was renamed tofantomas
so you didn't bump to the latest version.