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.

Sign up for GitHub

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

Jump to bottom

Deprecate getObject() in favour of getResult() #3

Open
fadion opened this issue Jul 27, 2016 · 1 comment
Open

Deprecate getObject() in favour of getResult() #3

fadion opened this issue Jul 27, 2016 · 1 comment

Comments

@fadion
Copy link
Owner

fadion commented Jul 27, 2016

Getting a Result class (as added in #2) is obviously more flexible than a dummy object. I'm thinking to deprecate getObject() in favour of getResult(). What do you think @djmarland?
@djmarland
Copy link
Contributor

I can agree with that. Personally I much prefer working with named classes than dummy objects.

@fadion fadion closed this as completed Mar 2, 2018
@fadion fadion reopened this Mar 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@djmarland @fadion