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

updated for new Play and RequireJS support #12

Merged
merged 2 commits into from
Feb 19, 2014
Merged

Conversation

jamesward
Copy link
Contributor

No description provided.

@huntc
Copy link
Contributor

huntc commented Feb 17, 2014

Thanks James. Do you think we should recommend just one way of doing this though... options can create confusion. I'd suggest we stick with the view approach.

It may also be worth checking back with the original angular-seed project to ensure synergy. That was always the intent with this project ie it should closely resemble angular-seed.

@jamesward
Copy link
Contributor Author

The server-side templating option is much more common. So I removed the other one.

huntc added a commit that referenced this pull request Feb 19, 2014
updated for new Play and RequireJS support
@huntc huntc merged commit d5eed2b into master Feb 19, 2014
@jamesward jamesward deleted the new-requirejs-support branch March 22, 2014 16:28
@jamesward
Copy link
Contributor Author

@plalloni Want to fork this template and do a new one with the static-only approach? I think it's easy to understand things if there is only one way presented in each template.

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.

4 participants