- 🇦🇺Australia acbramley
Currently Config::resetOverriddenData() completely removes the overriddenData class's property instead of reset the property value.
/**
* Resets the current data, so overrides are re-applied.
*
* This method should be called after the original data or the overridden data
* has been changed.
*
* @return \Drupal\Core\Config\Config
* The configuration object.
*/
protected function resetOverriddenData() {
unset($this->overriddenData);
return $this;
}
the instruction unset($this->overriddenData); remove the class's property when the correct behaviour should be set overriddenData to NULL.
This is not a big deal in se but
1) it is not consistent (and IMHO this can be marked as a bug).
2) it can cause warning with code that use reflection (but this of course is not a strong point). Libs like Kint or Doctrine Debug are affected by this issue.
Make Config::resetOverriddenData() behaves consistently and reset only the VALUE of the property, not remove the class's property itself
Issue Summary update
Answer questions in #8 and #16
Postponed: needs info
11.0 🔥
Last updated
Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
