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

Use angular components #29

Open
grtjn opened this issue Nov 6, 2017 · 2 comments
Open

Use angular components #29

grtjn opened this issue Nov 6, 2017 · 2 comments

Comments

@grtjn
Copy link

grtjn commented Nov 6, 2017

To move a bit closer to Angular 2..

@patrickmcelwee
Copy link
Owner

I would also be interested in keeping as much of the code outside Angular as possible, as we've discussed before, so we could provide something useful to React / Vue implementations too. Redux let us do that before, so it would be worth thinking about whether that is a helpful way to organize the state and changes to the state. (Happy to discuss more ... I've been getting very familiar with Redux.)

@grtjn
Copy link
Author

grtjn commented Nov 7, 2017

Yes, this would only apply to the angular-wrapper part, angular 1 specifically.

Redux is probably a stage too high for me, (and less relevant to this ticket,) but we can definitely review again in later stage. How about a separate ticket for Redux state management?

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

2 participants