force CRLF on metadata retrieval?

[Dave Weeden]

Is there any way to configure IC to have line endings set to CRLF during metadata fetch operations?

I'm using a Windows machine which results in CRLF's when I pull code from github with the current configs, but the resultant files that come down from retrieve/refresh ops with IC have (just) LF's so I'm seeing lots of diff's that vary only by line endings.

I think I can probably get around this by putting tweaking the core.eol, core.autocrlf config settings and adding appropriate .gitattributes file entries but thought I should ask this group in case there's an easy way to have IC force CRLF on metadata fetch ops instead of LF.

I looked over the app config settings and nothing jumped out at me.

[Scott]

IC itself won't change line endings on retrieved files. As you mentioned, you can configure Git for the desired line endings to enforce them, or you can use an external diff tool that can be configured to ignore line endings (and other "unimportant" differences). I do both. Specifically I use Beyond Compare which is commercial (and easily worth it IMO), but there are free alternatives that have similar functionality.

Regards,

Scott Wells

[Dave Weeden]

Thanks for the very quick response!   I decided to add a .gitattributes in the source root with a single entry of '* text=auto eol=lf' which has fixed it for me.

I actually have a BC license which I use sometimes in standalone mode but I'm kind of hooked on the built in JB diff/merge functionality for on the fly arbitrary file/folder pairing analysis within projects.

That has proved hugely useful in de-duping code that I sometimes inherit from others in other languages/contexts so I figure I should stay the course with SF dev work for now.