Open pcdavid opened 3 weeks ago
One scenario to validate before we can actually remove our custom adapter is to define multiple View documents with references between them (typically through reused node description), and make sure they are correctly reloaded from scratch (editing domain disposed) with the inter-document references properly resolved.
It's not clear what it does (or more precisely, that what it does adds some value compared to EMF's default behavior). When replacing it with EMF's standard
ECrossReferenceAdapter
I don't see any regression (at least all the integration tests pass). Note that even in it's ownEditingContextCrossReferenceAdapterTest
, when not installing it intestMoveObject
the test still passes.It has at least one specific issue (#1400, though I can't reproduce it on master)
Note that we still need to install an
ECrossReferenceAdapter
becauseIncomingTreeDescriptionProvider
needs fast inverse cross references lookup (SysON too).