Translate state and lifecycle page - #39
Conversation
|
@tibuurcio what do you think about using |
|
@cezaraugusto I personally think leaving just Maybe I'm just used to see it being written as |
|
Also I was thinking, I think it could be |
I think that state can represent two different things and should be treated acordingly... When representing the current state of the application, as a snapshot in time, I don't think it loses semantic value if we translate it to "estado". I guess it only loses value when it's talking about Makes sense? |
|
@halian-vilela It makes sense, indeed :) |
halian-vilela
left a comment
There was a problem hiding this comment.
LGTM!
S贸 mudar essa 煤ltima coisinhas sobre o g锚nero das fun莽玫es.
Co-Authored-By: jhonmike <developer@jhonmike.com.br>
Co-Authored-By: jhonmike <developer@jhonmike.com.br>
|
Esse |
cezaraugusto
left a comment
There was a problem hiding this comment.
obrigado @jhonmike! pedi uns ajustes: um erro de ortografia e para capitalizar as palavras dos t铆tulos, como original. De resto t谩 贸timo pra mim.
WendellAdriel e eu j谩 realizamos o review desse PR e as altera莽玫es solicitadas j谩 foram feitas.
* translated the first part of the state and life cycle doc * translated section covert function for a class * translated section adding local state to class * translated section adding lifecycle methods to a class * translated section using state correctly * translated section the date flows down fix * Revert internal link translations * treating according to its context * Update content/docs/state-and-lifecycle.md Co-Authored-By: jhonmike <developer@jhonmike.com.br> * Update content/docs/state-and-lifecycle.md Co-Authored-By: jhonmike <developer@jhonmike.com.br> * leaving title in capital
#1
Sections: