vuejs / vuejs/docs

`It should be noted that the ref array does not guarantee the same order as the source array` - provide example (or remove)

Open
#1,961 2 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Vue
Stars
3.2k
Forks
5k
Avg merge
14d 17h
Merged PRs (30d)
1

Description

There's information in docs (https://vuejs.org/guide/essentials/template-refs.html#refs-inside-v-for) that the order of the elements of an array ref is not guaranteed.

It may restrain some developers from using <foo v-for="..." ref="someRef"> and make them search for another solution resulting in the correct order. However if the statement is valid only for very specific scenarios there should be some example(s) so that developers know whether their usecase would provide the correct order of elements or not.

If this is something that was just copied from Vue 2 and is not relevant any longer then it should be removed

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read the “Refs inside v-for” section of the template refs documentation linked in the issue, then verify whether array-ref order can differ from source order in any relevant scenario. Document a concrete example if the warning remains valid; otherwise remove the statement, and ensure the section clearly guides Vue users.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
Half a day
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.