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

Adapt to Angular renaming #213

Open
SethDavenport opened this issue Dec 23, 2016 · 2 comments
Open

Adapt to Angular renaming #213

SethDavenport opened this issue Dec 23, 2016 · 2 comments

Comments

@SethDavenport
Copy link
Contributor

SethDavenport commented Dec 23, 2016

How do we want to deal with the whole Angular2 -> Angular, Angular1 -> AngularJS thing?

@ShaunEvening
Copy link
Contributor

In the book we referred to 1.x as AngularJS and >=2 as Angular. When comparing the two we use specific version numbers to avoid confusion. It seems like the rangle-starter repo does a pretty good job of this already.

Perhaps renaming some of the angular2-* repos to angular-* in preparation for the release of ng4 in march would be a good idea?

@SethDavenport
Copy link
Contributor Author

Sure

I guess there are two things two consider:

  • how we call things in docs
  • the actual repo names.

For docs, what we've been doing in the gitbook seems reasonable. I've done something similar in the angular-redux docs (Angular 1.x, Angular 2+).

Don't think that will work for repo names though. In which case I'm thinking:

angular-redux-example -> angular1-redux-example
angular2-redux-example -> angular-redux-example

However that involves 'recycling' a name which will probably confuse github a lot. So I'd love to hear some suggestions :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants