This repository was archived by the owner on Feb 26, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
chore: update the codebase (e.g. directory layout, file naming etc) #334
Comments
gkalpak
added a commit
to gkalpak/angular-seed
that referenced
this issue
Aug 25, 2016
…n best practices Partly addresses angular#334.
gkalpak
added a commit
to gkalpak/angular-seed
that referenced
this issue
Oct 26, 2018
…n best practices Partly addresses angular#334.
gkalpak
added a commit
to gkalpak/angular-seed
that referenced
this issue
Oct 26, 2018
…n best practices Partly addresses angular#334.
Core makes it sound like it is part of AngularJS no? I could live with common or shared |
I personally prefer |
I am not going to fight over this one |
gkalpak
added a commit
that referenced
this issue
Oct 30, 2018
…n best practices Partly addresses #334.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Once/If #341 is merged, it would be a good idea to update the code organization to adhere to latest best practices™ and bring the seed closer to the tutorial (see angular/angular-phonecat#326). E.g.:
components/
tocore/
orcommon/
.Now that "components" means something different, it can be confusing.
_test.js
files to.spec.js
..module.js
.karma.conf.js
to account for the above changes.The text was updated successfully, but these errors were encountered: