Open Awk34 opened 8 years ago
Hi @Awk34 , thanks for the report! We don't have a repo that developers clone, instead we ask them to start a new project with the angular-fullstack generator, and then we walk them through some steps where they add features to the generated project. In this workflow I'm not sure how we'd remove the issues link from the default template?
Oh okay, I didn't see anything about using the generator itself when I quickly looked at the docs.
I noticed the two following example apps. That's why I made this issue. https://github.com/stormpath/stormpath-sdk-angularjs/tree/master/example/dashboard-app https://github.com/stormpath/stormpath-sdk-angularjs/tree/master/example/ng-route-app
But if users are instructed to just use the latest version of the generator themselves, issues from then on should be reported to us. Thanks :)
Ah sorry I wasn't looking at the example apps :) so we certainly can remove those links. And we do hope to upgrade to the new generator soon, so that will resolve that use case. Thanks again for the report, I love the angular generator, thank you for all the work that goes into it!
Per the plan in #166 the Yeomon sample app is going to be removed, so this issue can be closed at that time.
Hi, it looks like you guys used the Angular Full-Stack Generator to scaffold some example Angular apps for this. We have an 'Issues' link in the footer of those apps that points to the GitHub issues for the generator. I think you guys should change that to point to your repos Issues section instead. :)
Reference: https://github.com/angular-fullstack/generator-angular-fullstack/issues/2071