1.1.0 Smarter Mixin Merges #1003
Open
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
- Automatically promote mixin or config :defines and :flags lists to `*` matchers if mixin and config conventions do not match. - Enabled `:extend_existing_arrays` for `deep_merge()` to handle config / mixin merge cases of a value as a single string merged with an array of strings. - Added merge warnings to log any oddball edge cases where a mixin value would silently clobber a config value
- Spoke to the design intent and recommendation to think in terms of additive merges - Clarified merge rules - Limited reorganization of headings
Letme
reviewed
Mar 11, 2025
|
|
||
| Ceedling provides reasonably verbose logging at startup telling you which | ||
| configuration files were used and in what order they were merged. | ||
| configuration file and Mixins were used and in what order they were merged. |
There was a problem hiding this comment.
Suggested change
| configuration file and Mixins were used and in what order they were merged. | |
| configuration file and Mixins were used, and in what order they were merged. |
| with mixins. | ||
| 1. Leave entire sections in your base configuration blank and fill them | ||
| out by merging mixins. With this strategy, you might configure all | ||
| the basics in a base project configuration but merge into it the |
There was a problem hiding this comment.
Suggested change
| the basics in a base project configuration but merge into it the | |
| the basics in a base project configuration, but merge into it the |
|
|
||
| The example command line above will produce the following logging output. | ||
| The example command line above will produce the following logging output | ||
| if verbosity is increased beyond the default. |
There was a problem hiding this comment.
I assume this is a bit more understandable than if.
Suggested change
| if verbosity is increased beyond the default. | |
| when verbosity is increased beyond the default. |
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.
:definesor:flagsconfig or mixin conventions mismatch (array vs. matcher hash), the array is promoted to the hash-style*matcher automatically with a notice logging this modification.deep_merge()to handle the case of merging mixin single values into config arrays (typically a single string into an array of strings).