with directive

[rhyek]

What problem does this feature solve?

This would provide something akin to a with block. It would be useful to me especially in cases like the one shown here. During iterations where your context is essentially a superset of the current component's, you can't have a computed property that defines person since it would be different for every meeting.

There are, of course, ways around this. The most straightforward would be to set person on the meeting object during creation. The issue is that creating the object might be done in different ways (locally, initial data load, server broadcast, etc) and you would need to handle all those cases, preferably in a DRY manner.

It could be made to only work with v-for to avoid this.

What does the proposed API look like?

<template>
  <table>
    <tbody>
      <tr
        v-for="meeting in meetings"
        with="{ person: people.find(person => person.id === meeting.personId) }"
      >
        <td>{{ meeting.date }}</td>
        <td>{{ person.firstName }}</td>
        <td>{{ person.lastName }}</td>
      </tr>
    </tbody>
  </table>
</template>

<script>
export default {
  data() {
    return {
      people: [
        { id: 1, firstName: 'Felix', lastName: 'Hudson' },
        { id: 2, firstName: 'Gaby', lastName: 'Rápalo' }
      ],
      meeting: [
        { date: '2017-01-01', personId: 1 },
        { date: '2017-03-02', personId: 1 },
        { date: '2017-02-07', personId: 2 }
      ]
    }
  }
}
</script>

[nickmessing]

@rhyek, you could actually do a computed property for that.

[nickmessing]

Actually I do like the idea, but I would call it v-scope because it adds aditional values in scope that is already created by v-for.

[posva]

It's better to create a component for that and compute there only once the heavy operation you need

[rhyek]

@posva this is actually intended for one off computations you won't need anywhere else. It's simpler, quicker, and offers more readability.

For more complex and reusable computations and functionality, I always use the approach you mention.

[posva]

It's simpler, quicker, and offers more readability

It's quicker to add once you know the syntax, but it's one more thing to know and adds another way of doing the same thing. That said, I see the benefits and simplicity of it, I simply think it's better to use a component, even if it's just declared on one component, because if you know that way you know a more powerful way of abstracting things, and will probably understand better how to use components

[rhyek]

@posva, for computing one property such as I do in my example, I would probably use @nickmessing's suggestion, currently. If I need more complexity/functionality, I tend to use components for that. I agree with you that components are the most powerful option (in fact, I like them a lot), but for some cases it might feel a bit overkill.

IMO:

• One or maybe two computations: with or v-scope
• Two or more: @nickmessing's suggestion
• More than a few properties, use of any other view model functionality (watchers, methods, etc), own template, etc: Components

[posva]

Ok, still simpler to use a component for all cases ☺️

…

On Sat, 25 Mar 2017, 15:59 Carlos Gonzales, ***@***.***> wrote: @posva <https://github.com/posva>, for computing one property such as I do in my example, I would probably use @nickmessing <https://github.com/nickmessing>'s suggestion, *currently*. If I need more complexity/functionality, I tend to use components for that. I agree with you that components are the most powerful option (in fact, I like them a lot <http://codepen.io/rhyek/pen/vyxOdQ>), but for some cases it might feel a bit overkill. IMO: - One or maybe two computations: with or v-scope - Two or more: @nickmessing <https://github.com/nickmessing>'s suggestion - More than a few properties, use of any other view model functionality (watchers, methods, etc), own template, etc: Components — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#5269 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAoicSLXk8SIsvYTBLuf53FvY7wINbfuks5rpSvPgaJpZM4MniyD> .

[gebilaoxiong]

I think that it is not difficult to achieve this issue, but the template syntax check is a problem.

[rhyek]

I think with="{ person: people.find(person => person.id === meeting.personId) }" wouldn't really work because what happens if something other than an object is returned, right?

It could instead be something like:

      <tr
        v-for="meeting in meetings"
        v-scope="{ person: people.find(person => person.id === meeting.personId) }"
      >
        <td>{{ meeting.date }}</td>
        <td>{{ scope.person.firstName }}</td>
        <td>{{ scope.person.lastName }}</td>
      </tr>

[rhyek]

Another (maybe dumb) example:

<tbody>
  <template
    v-for="(meeting, index) of meetings"
    v-scope="{ class: [index % 2 === 0 ? 'even' : 'odd'] }"
  >
    <tr class="summary" :class="scope.class">
      ...
    </tr>
    <tr class="detail" :class="scope.class">
      ...
    </tr>
  </template>
</tbody>

You get the idea. @posva, you can't use components here because they can only have one root element. 😄

[posva]

Actually, you can, the tbody can be a component

[rhyek]

Using your method, the component would be per meeting. Edit: Nvm, I see what you mean.

…

On Mar 25, 2017 3:14 PM, "Eduardo San Martin Morote" < ***@***.***> wrote: Actually, you can, the tbody can be a component — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#5269 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAq5ype0LqlKiALnYvcSTXsc-tJD6327ks5rpYOxgaJpZM4MniyD> .

[gebilaoxiong]

@posva I think that in some cases he is right, everyone wants to write a little code to achieve more features ：）

[pbastowski]

@rhyek
What you are asking for is already available, but under a different disguise:

    p(
      v-for="(meeting, i, person=people.find(person => person.id === meeting.personId)) in meetings",
    )
        | {{ meeting.date }} |
        | {{ person.firstName }} |
        | {{ person.lastName }}

See http://jsbin.com/lelizuc/1/edit?html,js,output

[rhyek]

That's kinda funny. It definitely works and I think I actually like this syntax better. This is something that should maybe be mentioned in the guides?

Anyways, thank you @pbastowski.

Feel free to close the issue if so desired.

[rhyek]

Eh, apparently the expression in v-for can't be broken into different lines:

      <tr
        v-for="(
          meeting,
          index,
          person=people.find(person => person.id === meeting.personId)
        ) in meetings"
      >

Bummer.

[gebilaoxiong]

@rhyek I submitted a PR, hoping to help you

[gebilaoxiong]

@pbastowski In fact the above method does not solve all the situation, I think add for with in template is a better way

[pbastowski]

@gebilaoxiong My method solves the reported problem. I use this method myself.

So, just wondering, what problems does it not solve that a "with" directive will solve?

[gebilaoxiong]

@pbastowski There are a lot of ways to solve the problem, you also want to be able to maintain a good code, rather than write a line, is not it?

[pbastowski]

@gebilaoxiong Your statement and the following leading question is so broad that it can apply to any aspect of programming and perhaps even life itself :)

But seriously, I agree with you. A with directive would be a nice addition. Until then, my solution will probably help a few people, who like me, need this functionality now. I hope your PR gets merged.

[gebilaoxiong]

@pbastowski Sorry, i think for a moment, is there a better way?

Actually inside the vue, your method looks just a hack, if meettings is the object then person is always indexed and not the correct value.

https://vuejs.org/v2/api/#v-for

 <div v-for="(val, key, index) in object"></div>

Your method finally generates the code that's it like this:

  function (meeting, index, person = people.find(person => person.id === meeting.personId)) {
    // ...
  }

and also this method only supports one parameter, if there are multiple?

alias is used to store key, value, or index, and the with directive is to add other iterations. From the grammar can also be a good distinction.

My English is not very good, no intention to offend ：）

[pbastowski]

@gebilaoxiong Yes, that is correct. My method only works for iterating arrays, like in the question asked in this issue. Iterating objects would not work at all.

[CodinCat]

I feel it may over complexify the template syntax. Any of computed properties, methods and components can solve these problems easily.

[gebilaoxiong]

@CodinCat As I said, all roads lead to Rome. But we want to choose a good way ：）

• add method findPerson

  <tr v-for="(meeting, index) in meetings">
    <td>{{ meeting.date }}</td>
    <td>{{ findPerson(meeting.personId).firstName }}</td>
    <td>{{ findPerson(meeting.personId).lastName }}</td>
  </tr>

You can imagine, each field needs to be calculated once

• add computed properties
  can not be solved

• use component
  can be done，but need to provide a component
  looks a bit twists and turns

So I think the with directive is a good way, it does not need to add new members on vm, nor does it need to provide a component

you can use it like this

  <tr v-for="meeting in meetings"
    with="{ person: people.find(person => person.id === meeting.personId) }">
      <td>{{ meeting.date }}</td>
      <td>{{ person.firstName }}</td>
      <td>{{ person.lastName }}</td>
  </tr>

[Kingwl]

@gebilaoxiong
Add the computed properties of course can solve this

computedMeetings () {
    return this.meetings.map(meeting => Object.assign({}, meeting, {person: this.people.find(person => person.id === meeting.personId)}))
}

<tr v-for="meeting in computedMeetings">
  <td>{{ meeting.date }}</td>
  <td>{{ meeting.person.firstName }}</td>
  <td>{{ meeting.person.lastName }}</td>
</tr>

[gebilaoxiong]

@Kingwl Well, maybe I'm too horn, I just make a suggestion, use with You do not have to define a computed

[HerringtonDarkholme]

@rhyek @gebilaoxiong

I'm afraid with way is hardly scalabe.

Consider the trivial example above, it already has been quite verbose to specify I want an attendant in a meeting. Readabilty and conciseness is objective, but at least for me the proposed solution isn't the sweetiest syntax.

A larger component will probably worsen it. For example, you also want to show the attendant's meeting note in the component. More logic is crammed to with directive. The template will soon become unreadable and atrocious to modify. Note: we don't have, sadly, a decent syntax/type checker for expressions in template (correct me if I missed some awesome tool). To reduce the complexity of template one will move the logic to vm/script, which is contrary to the point of this proposal! The predicate in with directive will also become more complex. Consider: you want to display a person in meeting, but only if they is available according to their schedule. The function becomes with="{person: people.find(person => person.id === meeting.personId && person.schedule[meeting.time] === undefined)}", and it will become more complex with projects grow and requirements change.

A larger team will also worsen it. A programmer wants to skip a computed property, so does another programmer. In team work a with directive will, based on my own observation, promote more logic in template because one easywith directive added initially will grows to a huge code blob by different team members. We are always too lazy to add abstraction.

[gebilaoxiong]

@HerringtonDarkholme thx for your reply, I agree very much ：）

[rhyek]

Thank you all for your interest. I feel I agree with @HerringtonDarkholme and can see the issues this feature might develop for larger teams/projects. Using a computed property that maps my array or @pbastowski's solution are both good ways to provide the functionality I need.
I will close this issue now.