Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When creating a new contact, a Cozy Contact service is triggered with a
5 sec debounce. This service updates the contact and create a new _rev,
which can cause conflicts. And when conflicts arise, the contact is
never actually linked to the trip in database, making the feature
pointless. Even worse, the user was never informed about it, the error
being silent.
Fortunately, the Cozy realtime is there to dynamically updates the contact
with the new data.
Unfortunately, this was not properly handled: the contact itself was
never queried, and, once queried, never set in the state.
The conflicts should now be avoided, making the world a better place.
And for even more peace, see: cozy/cozy-client#1414