Currency 7.x-2.x uses external libraries with Yaml files that are used as configuration files. The idea was that in Drupal 8, these files could be used as default configuration. However, they are not located in ./path/to/module/config/, but instead in ./path/to/module/vendor/.... By adding a property to .info files, we can tell the system to look for config in a different directory.

CommentFileSizeAuthor
#3 drupal_1928324_01.patch872 bytesxano
#1 drupal_1928324_00.patch871 bytesxano

Comments

xano’s picture

xano
he/they
Primary language English
Location Southampton
commented
Status: Active » Needs review
StatusFileSize
new drupal_1928324_00.patch871 bytes

Untested, without updated tests, but it shows what I mean.

Status: Needs review » Needs work

The last submitted patch, drupal_1928324_00.patch, failed testing.

xano’s picture

xano
he/they
Primary language English
Location Southampton
commented
Status: Needs work » Needs review
StatusFileSize
new drupal_1928324_01.patch872 bytes

I told you it was untested.

xano’s picture

xano
he/they
Primary language English
Location Southampton
commented

An alternative would be to split up config_install_default_config() in a function that takes a directory and imports all config it finds in there. That may actually be better, because it imposes /config as a config directory on developers, because they will actually have to put in an effort to deviate from that.

alansaviolobo queued 3: drupal_1928324_01.patch for re-testing.

Status: Needs review » Needs work

The last submitted patch, 3: drupal_1928324_01.patch, failed testing.

andypost’s picture

andypost
he/him
Primary language Russian
commented
Issue summary: View changes

looks this outdated

xano’s picture

xano
he/they
Primary language English
Location Southampton
commented
Status: Needs work » Closed (won't fix)

I am closing this as I have come to the realization that it's not a good idea to pretend something is what it's not. In my case writing a custom config importer was the best solution.