slemesle / selma Goto Github PK

this behaviour should work for both primitive and boxed type.

isBoolean -> setBoolean
getBoolean -> setBoolean

We should be able to map field named "a" to field named "b"

Compilation should fail when fields in destination bean are note populated with a pretty error message.

Given an interface with two listed methods, let say:

 public interface FailingMapperGeneratedCode {

   PersonOut asPersonOut(PersonIn in);

  AddressOut asAddressOut(AddressIn in);

}

Where Person beans has a property address, Selma should use asAddressOut method for mapping instead of generating another one.

Build a system avoiding cyclic mapping, to avoid infinite loop.
In situation where two references them each other.

The current Factory system uses reflection to call class constructors, so it will only fail at runtime.

This is BAD, we should find another way.
adding a beanConstructorParam to the Mapper annotation or support for annotated parameter in the mapping signature should do the Job.

The idea here is to list the properties Selma can ignore on mapping code generation.

The mapping code generation should not use fields.

it should be possible to define a default value for enum conversion when in enum values does not fit in out enum.

public enum In {
VAL_1,VAL_2,VAL_3,VAL_4
}

public enum Out {
VAL_1,VAL_2
}

at least default missing values to null.

For custom mapper class, it should possible to define mapping as instance method and not only as static one.

The mapper should be able to map n-dimensions array.

In the provided examples there is no sample for the custom mapper (that I could find) the documentation is understandably very limited but that makes the feature unclear ...