- Issue created by @joegraduate
- First commit to issue fork.
- 🇮🇳India sakthi_dev
As if there is no config files in config sync then it is not required to validate the config ignore on Import. Please review.
- Status changed to Needs review
10 months ago 2:40pm 25 March 2024 - 🇺🇸United States joegraduate Arizona, USA
Added a test (
ConfigIgnoreTest::testSynchronizeForm()
) and also applied the fix forConfigIgnoreTest::testSettingsForm()
from 📌 Fix test failures on GitLab CI Needs review . - 🇺🇸United States joegraduate Arizona, USA
Merge requeset !25 should be ready for serious review now. I added a new test that demonstrates the issue without the other changes in the MR (see the failed tests-only pipeline result on GitLab CI).
I was unable to get that test to fail until I added a step to install the core field module so I've also updated the issues summary to indicate that this issue only occurs when the core field module is installed.
- Status changed to Needs work
10 months ago 8:26pm 27 March 2024 - 🇨🇭Switzerland bircher 🇨🇿
I see, maybe there is some special logic to check if the whole storage is empty and then not do any further checks and so on an empty storage we should not add stuff that gets ignored.
Fantastic work on the MR!
But instead of checking the sync storage we should check the transformation storage and make sure it is in the default collection. I don't see why we would need to know what is in the sync storage at that point. - Status changed to Needs review
10 months ago 12:06am 28 March 2024 - 🇺🇸United States joegraduate Arizona, USA
Thanks @bircher!
I've tried to implement your suggestions in the MR. This should be ready for review again.
- 🇺🇸United States joegraduate Arizona, USA
Uploading static patch of current MR changes for use with composer.
-
bircher →
committed 8e4d2e6b on 8.x-3.x authored by
sakthi_dev →
Issue #3432315 by joegraduate, sakthi_dev, bircher: Do not ignore on...
-
bircher →
committed 8e4d2e6b on 8.x-3.x authored by
sakthi_dev →
- Status changed to Fixed
10 months ago 10:29am 14 April 2024 - 🇨🇭Switzerland bircher 🇨🇿
I moved the return statement so that we don't have to check for the default collection. And I removed the check for the direction because exporting will never have it empty unless some other event subsciber empties it and in that case I guess it would be better also to leave it empty.
Thanks for the contribution!
Automatically closed - issue fixed for 2 weeks with no activity.
- 🇧🇷Brazil henrique-liduario
If you change the path of the synchronization directory, and delete all the files in the previous directory, the error will also occur, even if you are not using config_ignore, as is my case.