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.

Sign up for GitHub

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

Jump to bottom

effects(chore): update strategy #110

Closed
axtho opened this issue Jun 10, 2017 · 2 comments
Closed

effects(chore): update strategy #110

axtho opened this issue Jun 10, 2017 · 2 comments
Labels
store
Milestone
Backlog

Comments

@axtho
Copy link
Contributor

axtho commented Jun 10, 2017

when updating/ adding data we need to follow this convention:

  1. Update store
  2. Update middleware (like ngrx/db or pouchDb)**
  3. Update API
  4. Return (and compare) results from API
  5. Handle errors (roll back changes to store and middleware?)
@axtho axtho added the store label Jun 10, 2017
@axtho axtho added this to the 2.0.0 milestone Jun 10, 2017
@axtho
Copy link
Contributor Author

axtho commented Jun 18, 2017

ngrx v4 will likely add db (IndexDB) soon. This may be a good solution to cater for offline content

@axtho axtho mentioned this issue Jun 30, 2017
Closed
@axtho axtho modified the milestones: 2.0.0-beta.1, Backlog Oct 17, 2017
axtho added a commit that referenced this issue Dec 20, 2017
@axtho
working on #180, #110
aa39afe
@axtho
Copy link
Contributor Author

axtho commented Mar 7, 2018

closing in favour of #163

@axtho axtho closed this as completed Mar 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
store
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
1 participant
@axtho