-
-
Notifications
You must be signed in to change notification settings - Fork 190
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
Error formatting defines #if (!DEBUG) ... #endif (no #else) #2098
Labels
Comments
nojaf
added a commit
to nojaf/fantomas
that referenced
this issue
Feb 16, 2022
nojaf
added a commit
that referenced
this issue
Feb 16, 2022
The problem was indeed very similar. |
Fantastic, no rush as it is by no means a critical project but yes a release would be appreciated, I'll continue testing my Bolero project when the fix is in. |
Great, I'll probably pick this up on Friday. |
Thanks, using |
Thanks for confirming! |
jindraivanek
pushed a commit
to jindraivanek/fantomas
that referenced
this issue
Mar 30, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue created from fantomas-online
Code
Error
Problem description
Please describe here the Fantomas problem you encountered.
Check out our Contribution Guidelines.
Trying to format ASP.NET-style code which uses
#if (!DEBUG)
to remove certain logging. Originally I was using #if RELEASE and found out this isn't the way to go about it.Happy to try and fix this if you can point me in the right direction.
Extra information
Options
Fantomas master branch at 1/1/1990
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: