- Issue created by @tedbow
In
π
Add rudimentary conflict prevention to the Config Auto-save end-point
Active
updated the auto-save conflict detect test coverage to also cover Javascript components and Asset libraries. There were caching implications to the change in that issue because autoSaveStartingPoint
value is created by the loading the save entity.
Unfortunately, the test coverage is still kernel tests which can't properly test caching, see \Drupal\Core\PageCache\RequestPolicy\CommandLineOrUnsafeMethod
We need to convert all the tests that use \Drupal\Tests\experience_builder\Kernel\AutoSave\AutoSaveConflictTestTrait
into functional tests to test caching
Active
0.0
Auto-save