This repository was archived by the owner on Jan 20, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 100
Tradução completa do arquivo using-fragments.md #136
Merged
jessescn
merged 9 commits into
gatsbyjs:master
from
fbandeirac:traducao-{using-fragments.md}
Jan 9, 2020
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
400b959
Tradução completa do arquivo using-fragments.md
fbandeirac 452a6eb
Update docs/docs/using-fragments.md
fbandeirac a1d3756
Update docs/docs/using-fragments.md
fbandeirac 777647e
Update docs/docs/using-fragments.md
fbandeirac 653b655
Update docs/docs/using-fragments.md
fbandeirac 30a9315
Update docs/docs/using-fragments.md
fbandeirac 019cccf
Update docs/docs/using-fragments.md
fbandeirac 35d0344
Update docs/docs/using-fragments.md
fbandeirac 1e0865d
Update docs/docs/using-fragments.md
fbandeirac File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
O que você acha, será que não deveriamos traduzir
FragmentName
eTypeName
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Meu pensamento inicial foi o seguinte: FragmentName é o nome dado pelo desenvolvedor para o Fragmento, não é um termo específico em inglês. Então achei que a compreensão do tipo de informação para quem está iniciando ou não sabe inglês seria mais fácil estando traduzido, evitando confusão com o resto do código. TypeName eu traduzi pq, apesar de tecnicamente fazer parte do código (pensando que será substituído por umTypeName em inglês), imaginei que, na parte do manual que abordar os TypeNames, o termo seria traduzido, já que é apenas referencia a termos.
Com a sugestão de manter o termo original, imaginei que se trata de algum padrão já adotado em outras partes da tradução, e aí já acatei.