Enableable ArrayNodeDefinition is disabled for empty configuration #25874
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
Member
|
see #25891 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#25789 broke yaml's
~syntax because hereNULLis converted to[].It has to be converted because
ContainerBuilder:;loadFromExtensionexpects an array, but I have no clue how can we differentiate these two different states now withou leaking config component implementation details.8669a21 reproduced issue, and 73ee9a1 presents the simplest way to fix regression.
That's the only idea I got, but as I said, we are leaking implementation details here :(
Any ideas?