Fixed missing braces around passed on key values #407
Merged
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.
The received values of some keys or options may contain unescaped comma (
,
) and/or equal (=
) characters which may break key-value processing, for examplebreakbefore
,breakafter
, andbreak...symbol(pre|post)
options.So in user input, such values need to be enclosed in a pair of braces, e.g.,
breakafter={,]}
. Those braces are then removed in the extracted values (,]
). Then to pass on them to other keys/options, the values need to be braced again.This PR adds the required braces around forwarded key values, and updates
breakbefore
andbreakafter
docs to sync with gpoore/fvextra@16de52d (breakbefore and breakafter now support the escaped comma , (closes #15), 2022-11-10).Example