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

@AndroidParcelable to check before adding blank constructor #97

Open
tobykurien opened this issue Jan 26, 2016 · 2 comments
Open

@AndroidParcelable to check before adding blank constructor #97

tobykurien opened this issue Jan 26, 2016 · 2 comments
Assignees

Comments

@tobykurien
Copy link
Owner

Currently it forcefully adds a blank constructor and doesn't allow you to add your own

@Buggaboo
Copy link
Contributor

I tried fixing this today, but for some reason, the compiler does not acknowledge the empty ctors that were generated by the AndroidParcelable active annotation.

You may wanna have a go at it.

I don't know if it's a bug. We could throw an error if the user doesn't explicitly provide one.

@tobykurien
Copy link
Owner Author

Not sure if we're missing each other - what I meant by this issue is
that if I create a bean and add an empty constructor, then add the
@AndroidParcelable annotation, I get a compile error because there
are now 2 empty constructors. If @AndroidParcelable first checked
that the empty c'tor exists, then it can bypass adding it's own, and
hence no compile error :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants