-
-
Notifications
You must be signed in to change notification settings - Fork 193
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
Reordering comments on modules #2141
Comments
In case it helps my case: (Apologies if this crosses into stylistic discussion. It came as a behaviour change between versions which I wanted to check on. I can seek a ruling elsewhere) |
Hey Colin, please try out https://www.nuget.org/packages/fantomas-tool/4.7.2 |
Amazing response time, thanks! As a "reward" I've got more reports incoming. :-) |
🙈😅 I already regret publishing 4.7 🙃 |
Ah ha, you've already caught at least one: #2143 |
Yep, this going to be a bigger evil than I anticipated. |
btw generally 4.7 is a nice improvement for us, fixes a bunch we were marked as ignore or manually reverting. |
That is nice to hear, thank you for this feedback. |
Issue created from fantomas-online
Code
Result
Problem description
It's not exactly an issue but it's a change between Fantomas 4.6.0 and 4.7.1 - I can narrow down the version where it occurred if that helps.
We have a somewhat common requirement to stick a copyright at the top of files to make lawyers happy. That copyright (with
//
) is now swapped with module level code comments (with///
). It all works but it's fairly ugly.No problem if this is intended behaviour, I'll find a way around it if needed.
Extra information
Options
Fantomas master branch at 2022-03-10T17:18:56Z - c455e63
Default Fantomas configuration
Did you know that you can ignore files when formatting from fantomas-tool or the FAKE targets by using a .fantomasignore file?
The text was updated successfully, but these errors were encountered: