The definition of one-way data flow is confusing
Ninguém assumiu esta issue ainda.
- Linguagem predominante
- JavaScript
- Estrelas
- 11.8k
- Forks
- 7.9k
- Merge médio
- 1d 11h
- PRs com merge (30d)
- 11
Descrição
I was researching about data binding concept.
then found followings.
one-way data bindingtwo-way data binding
What I understand about data binding is about how Data and View are affecting each other.
one-way data bindingis using event-listener function to achieveView to DataData to Viewtogether.
(i.e, displaying input value in<p>tag.)two way data bindingis using the binding syntax (not using event-listener) and it can achieveView to DataData to View
(i.e, displaying input value in<p>tag.)
but when I read the official React document on react.dev.
It talks about one way data flow which is a bit confusing expression then it says this concept is about top to bottom parent to child. (which is completely different from the definition of one-way data binding).
// from the link below.
Remember: React uses one-way data flow, passing data down the component hierarchy from parent to child component.
https://react.dev/learn/thinking-in-react#step-4-identify-where-your-state-should-live
then when it talks about two way data binding the document brings displaying the input value on screen.
Which is not related to topic about Top to Bottom.
// from the link below.
React makes this data flow explicit, but it requires a little more typing than two-way data binding. If you try to type or check the box in the example above, you’ll see that React ignores your input.
https://react.dev/learn/thinking-in-react#step-5-add-inverse-data-flow
I feel like this concept needs to be updated to clarify the concept of data binding.
or if the document content is correct, Can someone explain what I am missing or confused about this document?
Guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Direção de pesquisa
Comece pelas seções vinculadas de Thinking in React, especialmente “Identify Where Your State Should Live” e “Add Inverse Data Flow”, e compare como elas usam “one-way data flow” e “two-way data binding”. Considera-se concluído quando a documentação distinguir claramente esses conceitos ou explicar a terminologia que causou a confusão.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- javascript, react
- Domínio
- documentation
- Tipo de issue
- Documentação
- Dificuldade
- 3/5
- Tempo estimado
- 1-2 dias
- Status de atividade
- Estagnada
- Clareza
- Precisa de esclarecimento
- Facilidade para iniciantes
- 35/100