Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Install
Works with Drupal: ^8 || ^9Using Composer to manage Drupal site dependencies
Alternative installation files
Download config_filter-8.x-1.7.tar.gztar.gz
27.5 KB
MD5: ba67eaabc63f786e4538cb2b9483f7b4
SHA-1: 2bfe81874f0c0f21067f90df2120677cab8f24a9
SHA-256: a8ab4f657b7ef5c4fd5ef5e6e45b33f36eb0d7bb350091cea13a4bdd0b6cb324
Download config_filter-8.x-1.7.zipzip
47.06 KB
MD5: c3cb5a1f1f6e84c6e9233c35538b0017
SHA-1: dc7edf6025e6cb837414b56bdb8a4c4c83dbb1ab
SHA-256: 3944e855bcde6808a70a6e1bf7026254cd79043dfb1a8cbf57e1e09adb38eade
Release notes
This release has a new test trait together with 8.x-2.2
See Issue #3173393
/**
* Trait to easily test import and export of config by comparing storages.
*
* The "new" config storage transformation API which was added to drupal 8.8
* transforms the storage before importing and exporting via the event system.
* This is a very different API from Config Filter 1.x but they work together.
*
* This test trait aims to provide methods to guide developers writing tests
* that work independently of whether the module uses Config Filter plugins or
* the new core events. You do this by comparing what you expect to be imported
* or exported.
*
* Drupal core <8.8 with config filter:
* export:
* [active] ----------------------------------------> [filter wrapping [sync]]
* import:
* [filter wrapping [sync]] ----------------------------------------> [active]
*
* Drupal core >=8.8:
* export:
* [active] ---------------> [export transformation] -----------------> [sync]
* import:
* [sync] -----------------> [import transformation] ---------------> [active]
*
* The test for exporting should set up the active store by saving config and
* what is expected to be exported and then compare the export storage with it.
* The test for importing should set up the sync store by writing files (or by
* saving arrays to the FileStorage) and then comparing the expectations with
* the import storage.
*
* Tests using this trait will work with Config Filter 1.x and 2.x and they will
* also work when using the core api directly provided the module has the same
* behaviour with the event listener as with the config filter plugin.
*
* @see \Drupal\Tests\config_filter\Kernel\ExampleStorageKernelTest
*/
trait ConfigStorageTestTrait