blocks|key|1144193|text|我认为这是不可能的。你可以重用"node“，但不能是它的一部分。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1144194|bill-to:+&id001
++++given++:+Chris
++++family+:+Dumars
ship-to:+*id001|code-block|syntax|javascript|1144195|这是完全有效的YAML，字段given和family在ship-to块中被重用。您可以以同样的方式重用标量节点，但是您无法更改其内部内容，并从YAML内部将路径的最后一部分添加到该节点。|offset|length|style|CODE|1144196|如果重复如此困扰您，我建议让您的应用程序意识到root属性，并将其添加到每个看起来相对而不是绝对的路径中。|1144197|entityMap^0|0|0|E|5|K|6|R|7|0|N|4|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@$I|T|J|U|K|L]|$I|V|J|W|K|L]|$I|X|J|Y|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|Z|8|@$I|10|J|11|K|L]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|P|$]]

I don't think it is possible. You can reuse "node" but not part of it. 

<pre><code>bill-to: &amp;id001
 given : Chris
 family : Dumars
ship-to: *id001
</code></pre>

This is perfectly valid YAML and fields <code>given</code> and <code>family</code> are reused in <code>ship-to</code> block. You can reuse a scalar node the same way but there's no way you can change what's inside and add that last part of a path to it from inside YAML.

If repetition bother you that much I suggest to make your application aware of <code>root</code> property and add it to every path that looks relative not absolute.

blocks|key|1144210|text|是的，使用自定义标签。在Python语言中的示例中，使用!join标记连接数组中的字符串：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1144211|import+yaml

##+define+custom+tag+handler
def+join(loader,+node):
++++seq+=+loader.construct_sequence(node)
++++return+''.join([str(i)+for+i+in+seq])

##+register+the+tag+handler
yaml.add_constructor('!join',+join)

##+using+your+sample+data
yaml.load("""
paths:
++++root:+&BASE+/path/to/root/
++++patha:+!join+[*BASE,+a]
++++pathb:+!join+[*BASE,+b]
++++pathc:+!join+[*BASE,+c]
""")|code-block|syntax|javascript|1144212|这会导致：|1144213|{
++++'paths':+{
++++++++'patha':+'/path/to/root/a',
++++++++'pathb':+'/path/to/root/b',
++++++++'pathc':+'/path/to/root/c',
++++++++'root':+'/path/to/root/'
+++++}
}|1144214|!join的参数数组可以有任意数量的任意数据类型的元素，只要它们可以转换为字符串，因此!join+[*a,+"/",+*b,+"/",+*c]的作用正如您所期望的那样。|1144215|entityMap^0|S|5|0|0|0|0|0|5|17|S|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|W|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|Y|8|@$9|Z|A|10|B|C]|$9|11|A|12|B|C]]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|13|8|@]|D|@]|E|$]]]|R|$]]

Yes, using custom tags. Example in Python, making the <code>!join</code> tag join strings in an array:

<pre class="lang-python prettyprint-override"><code>import yaml

## define custom tag handler
def join(loader, node):
 seq = loader.construct_sequence(node)
 return ''.join([str(i) for i in seq])

## register the tag handler
yaml.add_constructor('!join', join)

## using your sample data
yaml.load("""
paths:
 root: &amp;BASE /path/to/root/
 patha: !join [*BASE, a]
 pathb: !join [*BASE, b]
 pathc: !join [*BASE, c]
""")
</code></pre>

Which results in:

<pre><code>{
 'paths': {
 'patha': '/path/to/root/a',
 'pathb': '/path/to/root/b',
 'pathc': '/path/to/root/c',
 'root': '/path/to/root/'
 }
}
</code></pre>

The array of arguments to <code>!join</code> can have any number of elements of any data type, as long as they can be converted to string, so <code>!join [*a, "/", *b, "/", *c]</code> does what you would expect.

blocks|key|1144241|text|看待这个问题的另一种方法是简单地使用另一个字段。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1144242|paths:
++root_path:+&root
+++++val:+/path/to/root/
++patha:+&a
++++root_path:+*root
++++rel_path:+a
++pathb:+&b
++++root_path:+*root
++++rel_path:+b
++pathc:+&c
++++root_path:+*root
++++rel_path:+c|code-block|syntax|javascript|1144243|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Another way to look at this is to simply use another field.

<pre><code>paths:
 root_path: &amp;root
 val: /path/to/root/
 patha: &amp;a
 root_path: *root
 rel_path: a
 pathb: &amp;b
 root_path: *root
 rel_path: b
 pathc: &amp;c
 root_path: *root
 rel_path: c
</code></pre>

blocks|key|1144295|text|我已经创建了一个库，可以在Packagist上找到，它执行以下功能：https://packagist.org/packages/grasmash/yaml-expander|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1144296|YAML文件示例：|1144297|type:+book
book:
++title:+Dune
++author:+Frank+Herbert
++copyright:+${book.author}+1965
++protaganist:+${characters.0.name}
++media:
++++-+hardcover
characters:
++-+name:+Paul+Atreides
++++occupation:+Kwisatz+Haderach
++++aliases:
++++++-+Usul
++++++-+Muad'Dib
++++++-+The+Preacher
++-+name:+Duncan+Idaho
++++occupation:+Swordmaster
summary:+${book.title}+by+${book.author}
product-name:+${${type}.title}|code-block|syntax|javascript|1144298|示例逻辑：|1144299|//+Parse+a+yaml+string+directly,+expanding+internal+property+references.
$yaml_string+=+file_get_contents("dune.yml");
$expanded+=+\Grasmash\YamlExpander\Expander::parse($yaml_string);
print_r($expanded);|1144300|结果数组：|1144301|array+(
++'type'+=>+'book',
++'book'+=>+
++array+(
++++'title'+=>+'Dune',
++++'author'+=>+'Frank+Herbert',
++++'copyright'+=>+'Frank+Herbert+1965',
++++'protaganist'+=>+'Paul+Atreides',
++++'media'+=>+
++++array+(
++++++0+=>+'hardcover',
++++),
++),
++'characters'+=>+
++array+(
++++0+=>+
++++array+(
++++++'name'+=>+'Paul+Atreides',
++++++'occupation'+=>+'Kwisatz+Haderach',
++++++'aliases'+=>+
++++++array+(
++++++++0+=>+'Usul',
++++++++1+=>+'Muad\'Dib',
++++++++2+=>+'The+Preacher',
++++++),
++++),
++++1+=>+
++++array+(
++++++'name'+=>+'Duncan+Idaho',
++++++'occupation'+=>+'Swordmaster',
++++),
++),
++'summary'+=>+'Dune+by+Frank+Herbert',
);|1144302|entityMap|0|LINK|mutability|MUTABLE|url|https://packagist.org/packages/grasmash/yaml-expander^0|Y|1H|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@$A|11|B|12|1|13]]|C|$]]|$1|D|3|E|5|6|7|14|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|15|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|16|8|@]|9|@]|C|$]]|$1|M|3|N|5|H|7|17|8|@]|9|@]|C|$I|J]]|$1|O|3|P|5|6|7|18|8|@]|9|@]|C|$]]|$1|Q|3|R|5|H|7|19|8|@]|9|@]|C|$I|J]]|$1|S|3|-4|5|6|7|1A|8|@]|9|@]|C|$]]]|T|$U|$5|V|W|X|C|$Y|Z]]]]

I've create a library, available on Packagist, that performs this function:
<a href="https://packagist.org/packages/grasmash/yaml-expander" rel="noreferrer">https://packagist.org/packages/grasmash/yaml-expander</a>

Example YAML file:


<pre><code>type: book
book:
 title: Dune
 author: Frank Herbert
 copyright: ${book.author} 1965
 protaganist: ${characters.0.name}
 media:
 - hardcover
characters:
 - name: Paul Atreides
 occupation: Kwisatz Haderach
 aliases:
 - Usul
 - Muad'Dib
 - The Preacher
 - name: Duncan Idaho
 occupation: Swordmaster
summary: ${book.title} by ${book.author}
product-name: ${${type}.title}
</code></pre>

Example logic:


<pre><code>// Parse a yaml string directly, expanding internal property references.
$yaml_string = file_get_contents("dune.yml");
$expanded = \Grasmash\YamlExpander\Expander::parse($yaml_string);
print_r($expanded);
</code></pre>

Resultant array:


<pre><code>array (
 'type' =&gt; 'book',
 'book' =&gt; 
 array (
 'title' =&gt; 'Dune',
 'author' =&gt; 'Frank Herbert',
 'copyright' =&gt; 'Frank Herbert 1965',
 'protaganist' =&gt; 'Paul Atreides',
 'media' =&gt; 
 array (
 0 =&gt; 'hardcover',
 ),
 ),
 'characters' =&gt; 
 array (
 0 =&gt; 
 array (
 'name' =&gt; 'Paul Atreides',
 'occupation' =&gt; 'Kwisatz Haderach',
 'aliases' =&gt; 
 array (
 0 =&gt; 'Usul',
 1 =&gt; 'Muad\'Dib',
 2 =&gt; 'The Preacher',
 ),
 ),
 1 =&gt; 
 array (
 'name' =&gt; 'Duncan Idaho',
 'occupation' =&gt; 'Swordmaster',
 ),
 ),
 'summary' =&gt; 'Dune by Frank Herbert',
);
</code></pre>

blocks|key|1144339|text|在某些语言中，您可以使用备用库，例如，tampax是YAML处理变量的实现：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1144340|const+tampax+=+require('tampax');

const+yamlString+=+`
dude:
++name:+Arthur
weapon:
++favorite:+Excalibur
++useless:+knife
sentence:+"{{dude.name}}+use+{{weapon.favorite}}.+The+goal+is+{{goal}}."`;

const+r+=+tampax.yamlParseString(yamlString,+{+goal:+'to+kill+Mordred'+});
console.log(r.sentence);

//+output+:+"Arthur+use+Excalibur.+The+goal+is+to+kill+Mordred."|code-block|syntax|javascript|1144341|编者按:+poster也是这个包的作者。|1144342|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/arthurlacoste/tampax^0|J|6|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|X|8|@]|9|@]|C|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

In some languages, you can use an alternative library, For example, <a href="https://github.com/arthurlacoste/tampax" rel="nofollow noreferrer">tampax</a> is an implementation of YAML handling variables:
<pre class="lang-js prettyprint-override"><code>const tampax = require('tampax');

const yamlString = `
dude:
 name: Arthur
weapon:
 favorite: Excalibur
 useless: knife
sentence: &quot;{{dude.name}} use {{weapon.favorite}}. The goal is {{goal}}.&quot;`;

const r = tampax.yamlParseString(yamlString, { goal: 'to kill Mordred' });
console.log(r.sentence);

// output : &quot;Arthur use Excalibur. The goal is to kill Mordred.&quot;
</code></pre>
Editor's Note: poster is also the author of this package.

blocks|key|1359455|text|使用Yglu，您可以将示例编写为：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1359456|paths:
++root:+/path/to/root/
++patha:+!?+.paths.root+%2B+a
++pathb:+!?+.paths.root+%2B+b
++pathc:+!?+.paths.root+%2B+c|code-block|syntax|javascript|1359457|免责声明:我是Yglu的作者。|1359458|entityMap|0|LINK|mutability|MUTABLE|url|https://yglu.io/^0|2|4|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|X|8|@]|9|@]|C|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

With <a href="https://yglu.io" rel="nofollow noreferrer">Yglu</a>, you can write your example as:

<pre><code>paths:
 root: /path/to/root/
 patha: !? .paths.root + a
 pathb: !? .paths.root + b
 pathc: !? .paths.root + c
</code></pre>

Disclaimer: I am the author of Yglu.

I have the following YAML:

<pre><code>paths:
 patha: /path/to/root/a
 pathb: /path/to/root/b
 pathc: /path/to/root/c
</code></pre>

How can I "normalise" this, by removing <code>/path/to/root/</code> from the three paths, and have it as its own setting, something like:

<pre><code>paths:
 root: /path/to/root/
 patha: *root* + a
 pathb: *root* + b
 pathc: *root* + c
</code></pre>

Obviously that's invalid, I just made it up. What's the real syntax? Can it be done?

how to reference a YAML "setting" from elsewhere in the same YAML file?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我有以下YAML：paths:  patha: /path/to/root/a  pathb: /path/to/root/b  pathc: /path/to/root/c我如何通过从三个路径中删除/path/to/root/，并将其作为自己的设置来“标准化”它，如下所示：paths:  root: /path/to...

问如何在同一个YAML文件中引用来自其他地方的YAML“设置”？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在同一个YAML文件中引用来自其他地方的YAML“设置”？EN