You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The thing is I can’t see any issues with AnglarJS caused by source files order.
I realized it when I saw that gulp-angular-filesort doesn’t actually sort files in a way I thought.
I’ve thought that gulp-angular-filesort looks at angular.module statements and sort files according to specified dependency in the brackets. It looks like I was wrong, ‘cause it doesn’t.
The text was updated successfully, but these errors were encountered:
But if each and every file defines their own modules there is no need for this plugin! Because then a module won't be used before it's been declared.
I am also quite certain that AngularJS was more picky when it came to module load order back in the day, but think it's solved now. So there may be more reasons to not use this plugin today than when it was first released. (I wouldn't know actually because I haven't used AngularJS in quite a while)
Side note: IMO this plugin shouldn't be used at all, use something like Browserify or Webpack instead!
The thing is I can’t see any issues with AnglarJS caused by source files order.
I realized it when I saw that gulp-angular-filesort doesn’t actually sort files in a way I thought.
I’ve thought that gulp-angular-filesort looks at angular.module statements and sort files according to specified dependency in the brackets. It looks like I was wrong, ‘cause it doesn’t.
The text was updated successfully, but these errors were encountered: