Skip to content
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

Use '\n' to join the template cache entries regardless of platform #126

Closed
wants to merge 1 commit into from
Closed

Use '\n' to join the template cache entries regardless of platform #126

wants to merge 1 commit into from

Conversation

edmorley
Copy link

Also leaves the template cache contents untouched, rather than using normalizelf().

This will ensure that developers using the same repo on different OSes will have identical grunt build output, avoiding constant churn when the built files are committed to the repository.

I've used '\n' for the joins since the rest of grunt-angular-templates uses it, as do other grunt plugins like grunt-contrib-uglify and grunt-usemin.

Fixes #125.

@ericclemmons, could you take a look? :-)

Also leaves the template cache contents untouched, rather than using
normalizelf().

This will ensure that developers using the same repo on different OSes
will have identical grunt build output, avoiding constant churn when the
built files are committed to the repository.

I've used '\n' for the joins since the rest of grunt-angular-templates
uses it, as do other grunt plugins like grunt-contrib-uglify and
grunt-usemin.

Fixes #125.
@edmorley
Copy link
Author

@ericclemmons, let me know if I need to do anything else before this can be merged :-)

@ericclemmons
Copy link
Owner

Going to merge this, but probably bump versions because people have varying opinions on the "right" linefeed ending =/

@edmorley
Copy link
Author

edmorley commented Jul 7, 2015

Ok, thank you :-)

@edmorley
Copy link
Author

@ericclemmons any news on this? :-)

@ericclemmons
Copy link
Owner

Would you be interested in #137? I need help...

@underscorebrody
Copy link
Collaborator

@edmorley What do you think about making this optional? Based on @edmorley's comment I think it might be the best approach. Default behavior would be the current handling of line feeds, but passing in the linefeed option with your preferred linefeed string would override it. Thoughts?

@edmorley
Copy link
Author

edmorley commented Feb 2, 2016

Would you be interested in #137? I need help...

Unfortunately I don't think I have the grunt expertise to help out at the moment. My team has also changed its deployment strategy, so we no longer run into this issue (the grunt build is performed on deploy instead of being committed to the repo).

If someone wants to take over the PR, they are most welcome :-)

@underscorebrody
Copy link
Collaborator

Created #154 as an alternative to this, going to close this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants