Skip to content
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

Merged
merged 5 commits into from
Jun 4, 2014
Merged

Doc - pt - Explanation about populate the objects. #572

merged 5 commits into from
Jun 4, 2014

Conversation

renanigt
Copy link
Contributor

@renanigt renanigt commented Jun 4, 2014

No description provided.

@renanigt
Copy link
Contributor Author

renanigt commented Jun 4, 2014

The text was based on discussion on the mailing list and the issue #566.
I removed the text "via getters", for me don't make sense because to populate the object we don't need the getters.

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

@renanigt renanigt changed the title Doc - Explanation about populate the objects. Doc - pt - Explanation about populate the objects. Jun 4, 2014
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:
Copy link
Member

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:"

@Turini
Copy link
Member

Turini commented Jun 4, 2014

I didn't translate to English because it's still not so good, but if you want, I can try.

After changes on PT docs, can you do that?

@renanigt
Copy link
Contributor Author

renanigt commented Jun 4, 2014

Your changes are importants and more clear.

I may try translate. 😃
Do I make this in this same branch or on another one ?

The changes are done.

@renanigt
Copy link
Contributor Author

renanigt commented Jun 4, 2014

The example classes was with annotation @Controller, so I removed now. 😁
I don't know where I was with my head. rsrs 😝

Sorry.

@Turini
Copy link
Member

Turini commented Jun 4, 2014

Do I make this in this same branch or on another one ?

same

@renanigt
Copy link
Contributor Author

renanigt commented Jun 4, 2014

Done.

So, now review my translation. rsrs :-)
Sorry for some possible errors. :P

@Turini
Copy link
Member

Turini commented Jun 4, 2014

hum, it's nice, but the follow content lost its meaning...
notice that after your additions, we have the add method:

public void add(Client custom) {
    dao.save(custom);
}

and there is no context or explanations for it.

@Turini
Copy link
Member

Turini commented Jun 4, 2014

maybe you should change for something like this:

Com isso podemos receber o custom como parâmetro do método add e o VRaptor vai cuidar de instanciar seus atributos:

public void add(Client custom) {
    dao.save(custom);
}

@renanigt
Copy link
Contributor Author

renanigt commented Jun 4, 2014

Good.

@renanigt
Copy link
Contributor Author

renanigt commented Jun 4, 2014

Done.

@Turini
Copy link
Member

Turini commented Jun 4, 2014

thanks

Turini added a commit that referenced this pull request Jun 4, 2014
Adding explanation about object's population.
@Turini Turini merged commit 9a7109b into caelum:master Jun 4, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants