-
Notifications
You must be signed in to change notification settings - Fork 11
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
Ignores not working on this method #93
Comments
That is odd, in my testing I can't reproduce this. I went and found the original file in the ColdBox repo and used the |
So weird. Would it matter that the formatting runs via the watch command?
Luis Majano
CEO
Ortus Solutions, Corp
1-888-557-8057
909-248-3408
www.ortussolutions.com
Support Open Source: www.patreon.com/ortussolutions
Linked In: https://www.linkedin.com/pub/3/731/483
Social: twitter.com/ortussolutions | twitter.com/lmajano
…On Nov 20, 2020, 12:39 PM -0600, John Berquist ***@***.***>, wrote:
That is odd, in my testing I can't reproduce this. I went and found the original file in the ColdBox repo and used the .cfformat.json file there and tried formatting it, and it didn't produce any extra line breaks.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
@lmajano I think I finally might know what is going on here. I was just talking with @bdw429s about how cfformat handles UTF-8 files with a BOM, and I realized that cfformat, while preserving the BOM correctly, was not parsing such files correctly. I cloned the ColdBox repo and checked, and the source file in question has a BOM. This is hopefully fixed now in the latest version of cfformat ( |
Ignores not working on this method for some reason:
It still manages to manipulate to this:
The text was updated successfully, but these errors were encountered: