Keeping this ticket around however we may need to discuss how conflict resolution strategies are implemented. With current API strategies will be just `one liners` and will provide no real value for developers. However we may go with the aproach where we will have 2 top level methods
*resolveOnClient* (currently implemented)
*resolveOnServer* where users can inject default behavior (aka previous concept of strategies)
This needs more discussion with wider team to get consensus.
This will be more clear to developers can will remove pointless functions like clientWins/serverWins. Strategies with deepMerge will have some quirks around circular dependencies etc. so I believe the real value will be to get users way to resolve on server and client. In terms of meeting trello criteria we still going to be fine as implementations are very trivial.
For example for client:
`resolveOnServer(()=> clientData)`
For example for server
`resolveOnServer(()=> serverData)`
ping [~aliok2] [~darahayes] [~stephencoady] |
|
