-
Type: Story
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
3
-
Needed
-
-
Iteration Icaco, Iteration Jackfruit, Iteration Kiwi, Iteration Lime, Iteration Maracuja
Feedback from drew.dipalma on this:
We’re seeing more and more issues with Compass/Data Explorer using a ‘replace’ vs. ‘update’ when changes are made – is this some that’s planned to change in the future?
The core of what’s causing this to come up more is that it’s emerging as a common pattern to test sync with an emulator + Compass/Explorer. However, as replace is being used when someone makes a change offline on an emulator and then changes in our tools the emulator update is overwritten even if the updates were to separate fields.
We’re still seeing the issue we talked about before around testing Triggers, but this new case is even less intuitive for users.
Open questions
- If we do nothing about this, will the VS Code extension have the same behavior when we implement document editing?
- is related to
-
COMPASS-5753 JSON editor is the only way to change _id
- Open
- related to
-
COMPASS-5528 Compass replaces whole array if you update one field in an array of objects
- Closed
- links to