Revert "Add a replacement mechanism to work around nil handling in ucfg (#4041)" #5044
Conversation
This file contains 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
pebrc
approved these changes
Nov 11, 2021
fantapsody
pushed a commit
to fantapsody/cloud-on-k8s
that referenced
this pull request
Feb 7, 2023
…fg (elastic#4041)" (elastic#5044) Since elastic/go-ucfg v0.8.4 now correctly renders empty arrays, we no longer need the nil replacement mechanism work around (elastic#4041). Also updates the unit test TestCanonicalConfig_Render to cover that the configuration with an empty array works.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Since elastic/go-ucfg#188 fixes #3718, we no longer need the replacement mechanism to work around nil handling in ucfg (#4041).
Also updates the unit test
TestCanonicalConfig_Renderto cover that the configuration with an empty array works.Resolves #3718.