blocks|key|3174461|text|鉴于您展示的示例，我建议使用选项2。它确实不是“在Aurelia上更容易”，但更明确的是，您将该属性的值绑定到所列的属性。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3174462|原来的答案在下面|offset|length|style|BOLD|3174463|第一个选项的好处是，例如，当您拥有一个接受多个值但作为单个字符串的属性时。这方面最常见的示例是class属性。class属性接受空格分隔列表中的多个类：|CODE|3174464|<div+class="foo+bar+baz"></div>|code-block|syntax|javascript|3174465|假设我们只想在离开其他类的同时，根据VM+baz上的一个支柱从这个列表中添加或删除类someProp。要使用.bind语法来实现这一点，我们必须在VM上创建一个具有完整列表的属性，但是按照someProp的值来添加或删除baz。但是使用字符串内插绑定，这就变得更简单了：|3174466|+<div+class="foo+bar+${someProp+?+'baz'+:+''}"></div>|3174467|您可以想象如何通过添加或删除多个类来扩展它。您也许可以使用.bind语法创建一个值转换器来实现这一点，但最终可能会出现一些可读性差的东西。|3174468|我可以想象，正在创建的值转换器可能类似于使用中的如下内容：|3174469|+<div+class.bind="someProp+%7C+toggleClass:'baz':'foo':bar'"></div>|3174470|我真的认为这比使用字符串内插语法的可读性低得多。|3174471|顺便说一下，我上面想象的值转换器应该是这样的：|3174472|export+class+ToggleClassValueConverter+{
++toView(value,+toggledClass,+...otherProps)+{
++++return+`${otherProps.join('+')}+${value+?+toggledClass+:+''}`;
++}
}|3174473|最好的部分是，我仍然在值转换器中使用字符串插值:-)|3174474|entityMap^0|0|0|6|0|1B|5|1J|5|0|0|L|3|16|8|1I|5|2M|8|32|3|0|0|T|5|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|19|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1A|8|@$D|1B|E|1C|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|1D|8|@$D|1E|E|1F|F|J]|$D|1G|E|1H|F|J]]|9|@]|A|$]]|$1|K|3|L|5|M|7|1I|8|@]|9|@]|A|$N|O]]|$1|P|3|Q|5|6|7|1J|8|@$D|1K|E|1L|F|J]|$D|1M|E|1N|F|J]|$D|1O|E|1P|F|J]|$D|1Q|E|1R|F|J]|$D|1S|E|1T|F|J]]|9|@]|A|$]]|$1|R|3|S|5|M|7|1U|8|@]|9|@]|A|$N|O]]|$1|T|3|U|5|6|7|1V|8|@$D|1W|E|1X|F|J]]|9|@]|A|$]]|$1|V|3|W|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|X|3|Y|5|M|7|1Z|8|@]|9|@]|A|$N|O]]|$1|Z|3|10|5|6|7|20|8|@]|9|@]|A|$]]|$1|11|3|12|5|6|7|21|8|@]|9|@]|A|$]]|$1|13|3|14|5|M|7|22|8|@]|9|@]|A|$N|O]]|$1|15|3|16|5|6|7|23|8|@]|9|@]|A|$]]|$1|17|3|-4|5|6|7|24|8|@]|9|@]|A|$]]]|18|$]]

Given the examples you have shown, I would recommend using option 2. It really isn't "easier on Aurelia," but it is more explicit that you are binding the value of that attribute to the property listed.

Original Answer Below

The benefit of the first option is when you have, for example, an attribute that accepts many values but as a single string. The most common example of this is the <code>class</code> attribute. The <code>class</code> attribute accepts multiple classes in a space-separated list:

<pre><code>&lt;div class="foo bar baz"&gt;&lt;/div&gt;
</code></pre>

Imagine we only want to add or remove the class <code>baz</code> from this list based on a prop on our VM <code>someProp</code> while leaving the other classes. To do this using the <code>.bind</code> syntax, we would have to create a property on our VM that has the full list but adds or removes <code>baz</code> as determined by the value of <code>someProp</code>. But using the string interpolated binding, this becomes much simpler:

<pre><code> &lt;div class="foo bar ${someProp ? 'baz' : ''}"&gt;&lt;/div&gt;
</code></pre>

You can imagine how this could be extended with multiple classes being added or removed. You could maybe create a value converter to do this using the <code>.bind</code> syntax, but it might end up with something that wasn't as readable.

I could imagine a value converter being created that might look something like this in use:

<pre><code> &lt;div class.bind="someProp | toggleClass:'baz':'foo':bar'"&gt;&lt;/div&gt;
</code></pre>

I really think this is much less readable than using the string interpolation syntax.

By the way, the value converter I imagined above would look like this:

<pre><code>export class ToggleClassValueConverter {
 toView(value, toggledClass, ...otherProps) {
 return `${otherProps.join(' ')} ${value ? toggledClass : ''}`;
 }
}
</code></pre>

The best part is that I'm still using string interpolation in the value converter :-)

blocks|key|2697343|text|在浏览了一下标签之后，我发现了这个。虽然这不是完全相同的事情，而且有点旧，但在https://github.com/aurelia/templating-binding/issues/24#issuecomment-168112829上有一件类似的事情是由Danyow先生(强调我的)谈论的|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2697344|是的，绑定行为的符号是&(而不是用于值转换器的值)。
<input+type="text"+data-original="${name+&+oneTime}"+value.bind="name"+/>
这里是编写一次性绑定的标准方法。--在解析和绑定方面，这将更加轻量级：
<input+type="text"+data-original.one-time="name"+value.bind="name"+/>|blockquote|style|CODE|BOLD|2697345|我不知道它是否适用于本例中的.+.bind/${name}情况以及oneTime实例，但如果引起他的注意，他可能会说两种方法。|2697346|考虑到这不是一个枯燥乏味的答案，我将把阿什利的答案标记为答案，因为它确认了清晰的问题，并提供了关于其他用例的有用信息，如果其他人使用类似的术语进行搜索的话。|2697347|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/aurelia/templating-binding/issues/24#issuecomment-168112829^0|13|26|0|0|R|21|3T|1X|39|8|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]]|C|$]]|$1|D|3|E|5|F|7|Z|8|@$A|10|B|11|G|H]|$A|12|B|13|G|H]|$A|14|B|15|G|I]]|9|@]|C|$]]|$1|J|3|K|5|6|7|16|8|@]|9|@]|C|$]]|$1|L|3|M|5|6|7|17|8|@]|9|@]|C|$]]|$1|N|3|-4|5|6|7|18|8|@]|9|@]|C|$]]]|O|$P|$5|Q|R|S|C|$T|U]]]]

After wading through the tabs I'd already opened I found this. Although it's not quite the same thing, and it's a bit old, there's a similar thing talked about on <a href="https://github.com/aurelia/templating-binding/issues/24#issuecomment-168112829" rel="nofollow noreferrer">https://github.com/aurelia/templating-binding/issues/24#issuecomment-168112829</a> by Mr Danyow (emphasis mine)

<blockquote>
 yep, the symbol for binding behaviors is &amp; (as opposed to | for value converters).
 
 <code>&lt;input type="text" data-original="${name &amp; oneTime}" value.bind="name" /&gt;</code>
 
 Here's the standard way to write a one-time binding. This will be a bit more light-weight in terms of parsing and binding:
 
 <code>&lt;input type="text" data-original.one-time="name" value.bind="name" /&gt;</code>
</blockquote>

I don't know if it applies to the .bind/${name} case as well as the oneTime one in the example, but perhaps if it comes to his attention he can say either way.

Given this isn't a cut and dry answer, I'll be marking Ashley's as the answer as it confirms the legibility question and provides useful information on other use cases should anyone else search on similar terms.

In our code base we have a mixture of the following:

<ol>
<li>attribute="${something}", attribute="${something | converter}", etc.</li>
<li>attribute.bind="something", attribute.bind="something | converter"</li>
</ol>

I find the latter easier to read.

The examples I'm referring to are exactly like the above; i.e., they do not add any additional string content.

I think that it's easier on Aurelia too. Am I correct?

Also, for these specific cases where no actual interpolation is
involved, is there any benefit to the first form? (other than it is
two characters less to type.)

.bind vs string interpolation in aurelia

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

在我们的代码库中，我们混合了以下内容：Attribute=“${某某}”，“attribute=”“${某某类转换器}”，等等。Attribute.bind=“某样”，attribute.bind=“某样东西”我觉得后者更容易读懂。我提到的示例与上面的完全相同；也就是说，它们不添加任何额外的字符串内容。我觉得对奥雷利亚...

问aurelia中的.bind与字符串插值
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问aurelia中的.bind与字符串插值EN