-
Notifications
You must be signed in to change notification settings - Fork 332
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doc - pt - Explanation about populate the objects. #572
Conversation
The text was based on discussion on the mailing list and the issue #566. I didn't translate to English because it's still not so good, but if you want, I can try. 😃 This pull request closes #566 |
Então os campos `name` e `address` do parâmetro `Client` que chamamos de `custom` no método `add` serão populados com `Paulo Silveira` e `R.Vergueiro` via getters e setters. | ||
Então os campos `name` e `address` do parâmetro `Client` que chamamos de `custom` no método `add` serão populados com `Paulo Silveira` e `R.Vergueiro` via setters ou construtor, utilizando parâmetros com os mesmos nomes dos atributos. | ||
|
||
Via Setters: |
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.
I'd change for something like: "Um exemplo via setters seria:"
After changes on PT docs, can you do that? |
Your changes are importants and more clear. I may try translate. 😃 The changes are done. |
The example classes was with annotation Sorry. |
same |
Done. So, now review my translation. rsrs :-) |
hum, it's nice, but the follow content lost its meaning... public void add(Client custom) {
dao.save(custom);
} and there is no context or explanations for it. |
maybe you should change for something like this:
public void add(Client custom) {
dao.save(custom);
} |
Good. |
Done. |
thanks |
Adding explanation about object's population.
No description provided.