This initial "bug" report is five years too late. It is now a major feature request.
Config collections are an undocumented subsystem that was introduced after this module was written. It would be ideal if we used them, as they should allow for full schema support. Schema validation is a nicety that only matters to programmers, so far as I can tell, so it is not an essential feature.
Problems that need to be overcome in order to support this initiative are:
I will not be working on this without dedicated, paid support, but I am happy to review code. Pull requests are preferred for work of this complexity.
Original post:
Using config_inspector module to validate config schemas we get "No schema" for every domain config override.
According to Drupal's documentation it is recommended to have schemas for configuration objects, see
https://www.drupal.org/docs/8/api/configuration-api/configuration-schema... →
Needs work
2.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
As far as I understand it, the issue will be irrelevant once we switch to Config Collections in version 3.
Now that this issue is closed, please review the contribution record.
As a contributor, attribute any organization helped you, or if you volunteered your own time.
Maintainers, please credit people who helped resolve this issue.