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

Refactor expense-pool, expense, and user service to have state. #184

Open
dting opened this issue Jul 25, 2016 · 0 comments
Open

Refactor expense-pool, expense, and user service to have state. #184

dting opened this issue Jul 25, 2016 · 0 comments

Comments

@dting
Copy link
Contributor

dting commented Jul 25, 2016

Currently our services are wrappers for $resource. Instead of having nested components and passing around state of various expense pools, expenses and users these services should have a local cache of these resources and give access to the $resource objects.

This will also provide a better abstraction of the models and controllers.

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

1 participant