Reviewed and tested in customer project. Seems to solve the problem and works.
joachim namyslo → credited metalbote → .
Simple reroll patch against 10.3.6
Simple reroll as needed by one of our projects against 10.3.6
Simple reroll
Reroll against new version...
Patch against 2.0.3, mr-diff does not apply because of reformattings in 2.x
Rebased against current 2.x
metalbote → made their first commit to this issue’s fork.
I stumbled across the following small flaw with the bottom border radius, my commit fixes it.
Current:
After:
Hovered version, and within will be same as before.
metalbote → changed the visibility of the branch 2118743-twig-debug-output-d10 to active.
This fixes also an error with `bcc`.
Just reroll for 10.1.6
Our workaround is now in config_filter/src/ConfigFilterEventSubscriber.phpL86 adding weight to the transform:
/**
* {@inheritdoc}
*/
public static function getSubscribedEvents() {
// @todo Use class constants when they get added in #2991683
$events['config.transform.import'][] = ['onImportTransform','-100'];
$events['config.transform.export'][] = ['onExportTransform'];
return $events;
}
So ignored configs will also ignored in the split folders, for now it seems to work, but still testing...
For me the same problem occured...and it is highly critical for any workflows.
a) config_split: Added system.menu.* to split, as menus may differ between environments.
b) config_ignore: Added system.menu.* to ignore, as menus could be created by a customer role
Expected behavior:
i) On drush cex, system.menu.my_new_prod_menu.yml gets exported to config/
ii) On drush cim, system.menu.my_new_prod_menu.yml with changes should be ignored.
iii) On drush cim, as system.menu.* is ignored, new menues on the system should not be deleted if there is no corresponding yml in config/
ii) & iii) do not behave as expected, and killed menus... anyway this cannot be the wanted feature set, can it?
Fix filename...
simple reroll
I changed this as we have already used 2.1.x-alpha for the d10/php8.1 compatibility...
Merged into dev, as we tested this on customer projects.
I close this issue as i will maintain this module in partnership with mirroar
Simple patch to avoid warning with explicit conversion...
Simple reroll...
@geoanders and everbody else, i will look into this module next week, as i have a very urgent customer project, which costs most of my time right now. Luckily, this module is also part of the project, therefore i have an already ported, and tested local port, so i hope to update the contrib aswell. Also further maintenance etc. i would also address next week, so i think comaintenance would be great, we also rely extremly on this module, and more hands solve more work ;-)
metalbote → created an issue.
Joachim Namyslo → credited metalbote → .
Just rerolled against 3.0.0-beta1
reroll...
+1 for Vue, sometimes ago there was this idea of Progressively Decoupled Drupal, vue serves this idea much better than react.