You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How we interpret remote and local differences, few examples:
269
+
270
+
previous state: x
271
+
new state : y
272
+
remote state: z
273
+
274
+
previous state: x
275
+
new state: y
276
+
remote state: x
277
+
278
+
remote-value is the same as last deployed, this is the default and not interesting, so it won’t be included in Changes.Remote
279
+
280
+
281
+
diff(savedState, remoteValue) —> no changes there, not interesting
282
+
283
+
284
+
previous state: x
285
+
new state: y
286
+
remote state: y
287
+
288
+
remote-value is different from last-deployed. One can say that because new-config and remote-value are converged on the same value, this should be noop/skip, but we’ve chosen to always act on local config changes, to avoid surprises.
289
+
290
+
291
+
To summarize, Remote.Changes is diff between previous state and remote state. If there are both local and remote actions, we take maximum possible action.
292
+
293
+
294
+
previous state: nil
295
+
new state: <irrelevant>
296
+
remote state: z
297
+
298
+
This is a case of server-side default being set. We’ll include it into Changes.Remote with action="skip” and reason="server_side_only”
0 commit comments