Inconsistent newlines in the source files #423
Comments
OK, so standardizing things is good, no question about it. Now, we need to weight benefits with the workload. To have consistent line endings in generated files we would have to:
@angular-ui/bootstrap what do you guys think? I'm really after standards and consistency but it shouldn't be just for sake of it, it must be helping the project. Personally I can work with any standard as loon it is agreed upon and automatically enforced so I don't have to waste brain cycles on those. @hlship a question for you - why did you need to edit build files? Was it a case of monkey-patching? |
@pkozlowski-opensource There's a lot of inconsistency in our code, but I'm not convinced of the value of standardizing everything - at least not when balanced against the requisite work. I would rather focus of features and testing. That said, if someone wants to ensure Unix-style line endings automatically (like through one of your methods above) I have no problem with that. |
+1 for the git option. We should be able to just put a
|
@ajoslin @joshdmiller so I had a close look into what is possible to be done automatically and it looks like we could get away with one setting in the git repo:
plus configuring grunt merge tasks to use @angular-ui/bootstrap if no one objects against switching to |
Edittng the aggregated files (ui-bootstrap-0.3.0.js) you can see that there's been a mix of Mac/Unix and Windows editors; many lines end with a ^M (carriage return) character.
The text was updated successfully, but these errors were encountered: