Minor improvement of variable naming accuracy

This commit is contained in:
cyqsimon 2023-11-02 20:35:58 +08:00
parent 64840fbbae
commit 0fea82cff9
No known key found for this signature in database
GPG key ID: 1D8CE2F297390D65
2 changed files with 5 additions and 4 deletions

View file

@ -172,10 +172,10 @@ impl MappingDefModel {
let list = self let list = self
.mappings .mappings
.into_iter() .into_iter()
.flat_map(|(target, matcher)| { .flat_map(|(target, matchers)| {
matcher matchers
.into_iter() .into_iter()
.map(|rule| (rule, target.clone())) .map(|matcher| (matcher, target.clone()))
.collect::<Vec<_>>() .collect::<Vec<_>>()
}) })
.collect(); .collect();

View file

@ -51,7 +51,8 @@ handle things like [XDG](https://specifications.freedesktop.org/basedir-spec/lat
All environment variables intended to be replaced at runtime must be enclosed in All environment variables intended to be replaced at runtime must be enclosed in
`${}`, for example `"/foo/*/${YOUR_ENV}-suffix/*.log"`. Note that this is the `${}`, for example `"/foo/*/${YOUR_ENV}-suffix/*.log"`. Note that this is the
**only** admissible syntax; other variable substitution syntaxes are not **only** admissible syntax; other variable substitution syntaxes are not
supported and are thus treated as plain text. supported and will either cause a compile time error, or be treated as plain
text.
For example, if `foo-application` also supports per-user configuration files, we For example, if `foo-application` also supports per-user configuration files, we
could write something like this: could write something like this: