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

Support component mappers with @Mapper in super classes #5

Open
GoogleCodeExporter opened this issue Nov 19, 2015 · 0 comments
Open

Comments

@GoogleCodeExporter
Copy link

The provided patch scans any super class of the provided entity system for 
fields with the @Mapper annotation. This allows the super class to declare 
component mappers and have them instanced by reflection.

I've also added a check to see if the field has already been instantiated 
(field.get (target) == null). This could be useful if a super class declares a 
static component mapper.
Declaring a static component mapper is not recommended, I suppose, but I figure 
its best to cover all bases in this case.

Original issue reported on code.google.com by seraphim...@gmail.com on 15 Oct 2012 at 1:12

Attachments:

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

No branches or pull requests

1 participant