Skip to content

migrate sample app to a more 'best practice' directory layout #961

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

Merged
merged 1 commit into from
Mar 13, 2014

Conversation

mbroadst
Copy link
Contributor

This is a somewhat invasive change, but I feel like it provides a few benefits:

  • it more closely follows the emerging "best practices" for angular app structure: best practice google doc
  • it shows how state management can be separated between modules
  • because there are multiple modules, it can serve as fertile ground for even more complicated examples

Please let me know what you think, or how I can improve upon this design. This was created as more of a thought experiment of applying the patterns described in the wiki to my own project, so I may have missed something.

@nateabele
Copy link
Contributor

Nice job. Please update the commit message to reflect the contributor guidelines, and I'll get this merged.

The current example is a bit too simplistic in my experience to fully grasp
the power of ui-router. It provides a monolithic example of state definition
that shows the varied approaches that can be used, but not in a very structured
format. This change applies the emerging best practice directory layout of an
angular application to exemplify the power of ui-router
@mbroadst
Copy link
Contributor Author

updated

@mbroadst
Copy link
Contributor Author

@nateabele also, what up philly ;)

@nateabele
Copy link
Contributor

Hey hey!

nateabele added a commit that referenced this pull request Mar 13, 2014
migrate sample app to a more 'best practice' directory layout
@nateabele nateabele merged commit b97a01d into angular-ui:master Mar 13, 2014
@mbroadst mbroadst deleted the improve-sample-structure branch March 13, 2014 18:08
@timkindberg
Copy link
Contributor

Hell yeah, thanks @mbroadst

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