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

Angular 2.0 #160

Open
Toxantron opened this issue May 31, 2016 · 9 comments
Open

Angular 2.0 #160

Toxantron opened this issue May 31, 2016 · 9 comments

Comments

@Toxantron
Copy link
Contributor

Since angular 2.0 seems to be around the corner we might want to start developing a version 2.0 of the library on a branch. What do you think?

@revolunet
Copy link
Owner

Hi, I'm not much into Angular apps anymore so can't help here but maybe @justinsa @adam187 @deltaepsilon ?

@Toxantron
Copy link
Contributor Author

If they are interested we could create a branch ng-2 and start porting the module. I'd be happy to contribute via PR against the branch.

@adam187
Copy link
Contributor

adam187 commented May 31, 2016

I'm also doing react mainly react nowadays :(

@Toxantron
Copy link
Contributor Author

Hopefully @justinsa is still on board. ;)

@Toxantron
Copy link
Contributor Author

I created a branch on my fork and will start porting to angular2 there. Anyone interested to join in is welcome. If this repo gets a branch I will open a PR.

@justinsa
Copy link
Collaborator

justinsa commented Jun 6, 2016

@Toxantron I may or may not get a chance to participate in this over the next two months.

@Toxantron
Copy link
Contributor Author

Would be nice to have you on board. The way I see it angular2 is still in beta and even after release I assume it will take some time before applications reach production state and require tracking.

And what would I do without your code reviews. ;)

@justinsa
Copy link
Collaborator

justinsa commented Jun 9, 2016

I am always happy to code review for you, just mention me in a comment on the code review and I will take a gander.

@Toxantron
Copy link
Contributor Author

Thanks. I think working with a sparing partner always yields better results. As soon as the branch approaches a state of migrating the libraries logic I will let you know.

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

No branches or pull requests

4 participants