- π«π·France dqd London | N.Y.C | Paris | Hamburg | Berlin
Confirmed that patch works by re-saving the existing references as expected - also on branch 5.0! so we maybe should set this issue to the latest dev like usual and create a backport for older releases if required. But I would strongly recommend to comment on code regarding this new behavior and to add tests. Also it is preferable to add this to a new release version with a change record linking to this issue. Otherwise users can be surprised by a new behavior not expected from before.
- Status changed to Needs work
over 1 year ago 5:43pm 14 September 2023 - π«π·France dqd London | N.Y.C | Paris | Hamburg | Berlin
Oops, wrong tag.
- π©πͺGermany Grevil
Haven't dived too deep into this issue, but if the proposed solution is simply a patch from another issue, shouldn't we just close this as a duplicate of π Complete Synchronization functionality for existing reference values Needs work and adjust its Title? There is also a newer patch provided in the linked issue.
- π©πͺGermany Anybody Porta Westfalica
Yes, closing this issue as duplicate of π Complete Synchronization functionality for existing reference values Needs work thanks for the heads-up @diqidoq!
- Status changed to Closed: duplicate
over 1 year ago 1:54pm 22 September 2023 - Status changed to Needs work
over 1 year ago 1:57pm 22 September 2023 - π«π·France dqd London | N.Y.C | Paris | Hamburg | Berlin
Yes this here should be closed in fav of π Complete Synchronization functionality for existing reference values Needs work
- Status changed to Closed: duplicate
over 1 year ago 1:57pm 22 September 2023 - π«π·France dqd London | N.Y.C | Paris | Hamburg | Berlin
Oops, @Anybody was faster :-)