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 "Partialify" to include templates #30

Merged
merged 1 commit into from Mar 28, 2015

Conversation

DrewML
Copy link
Contributor

@DrewML DrewML commented Mar 28, 2015

Howdy,

With this PR, I am recommending switching from the gulp-angular-templatecache plugin to the partialify plugin. Here are the reasons that make me believe this is a good choice:

  1. Adds template files to the dependency graph, which may be useful in larger projects if they plan to create per-page bundles for their builds.
  2. Removes the "magic" template paths you currently enter in the templateUrl field. When new developers use this boilerplate, they will likely be able to make more sense of a require call to a specific path on disk, instead of guessing why home.html just seems to work.
  3. Currently, the project builds a template.js file into a directory meant for source files. This removes that necessity, keeping the source directory cleaner.

@jakemmarsh
Copy link
Owner

Looks good, if you can just resolve the merge conflicts I'll merge it in!

…"magic" template paths, and to add html files to the dependency graph
@DrewML
Copy link
Contributor Author

DrewML commented Mar 28, 2015

Fixed merge conflicts, and cleaned up history a bit.

jakemmarsh added a commit that referenced this pull request Mar 28, 2015
Use "Partialify" to include templates
@jakemmarsh jakemmarsh merged commit 861919b into jakemmarsh:master Mar 28, 2015
jakemmarsh added a commit that referenced this pull request Apr 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants