- Issue created by @fgm
- 🇫🇷France fgm Paris, France
@sidharth_soman . OK, now "Ensure we do not need to dig further for a root cause"
- 🇳🇱Netherlands roderik Amsterdam,NL / Budapest,HU
Update to -dev (/git) instead.
The first (and at this moment, only) commit on top of v2.1.2 fix the issue for me, and is from 📌 #3360991 changed TypedConfigManager::createFromNameAndData() in 10.1.x Fixed (which seems to be still open with an extra patch, to... fix an equivalent drush command?)
(I'm not changing the status of this issue because the title is good for noobs like me who come across this error and search the issue queue. It can likely be closed as duplicate when a new version is released.)
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
I cannot reproduce this even when using Drupal core
10.0.x
and2.1.2
of the module.Perhaps this is a problem only on
10.1.x
? 🤔 If so, this would indeed probably be a duplicate of 📌 #3360991 changed TypedConfigManager::createFromNameAndData() in 10.1.x Fixed as @roderik seems to be implying 🤓In any case, just fixed 📌 #3360991 changed TypedConfigManager::createFromNameAndData() in 10.1.x Fixed , next up: this issue + 📌 Update ConfigInspectorManager::getNodeConstraints() for #3364109: NotNull + PrimitiveType is insufficient validation Fixed .
- Status changed to Closed: duplicate
about 1 year ago 2:33pm 22 August 2023 - 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
Confirmed that this is a duplicate of 📌 #3360991 changed TypedConfigManager::createFromNameAndData() in 10.1.x Fixed 👍
Tagging release shortly.
I will credit all of you on the other issue 😊